-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PATCH v3] doc: userguide: update code blocks #2154
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made two comments, one not really related to the changes donen here and the other so minor that feel free to ignore it.
Note that parsing is automatically done whenever classification is enabled | ||
for an RX interface (see below). | ||
receipt as controlled by the `odp_pktio_parser_config_t` struct. Note that | ||
parsing is automatically done whenever classification is enabled for an RX |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
parsing is automatically done whenever classification is enabled
This statement caught my eye even though it is not changed by this commit. I wonder if enabling of parsing is really guaranteed by the API in this case as I did not find it in the API text. Or perhaps this is just the way the linux-gen ODP implementation works?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed the API doesn't mention this, so removed the sentence.
----- | ||
Note that the *queue_param* field of this struct is ignored in DIRECT mode. | ||
The purpose of `odp_pktin_queue_config()` is to specify the number of PktIn | ||
`odp_pktin_queue_config()` API, which purpose is to specify the number of PktIn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 'which' does not sound quite right to me. I would probably use 'whose', or if that is not good, I would say "... API, the purpose of which is ...".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to whose
in V2.
e646c0e
to
84b1f22
Compare
Remove code sections copied from the API headers as they will not stay up- to-date. Update some code examples to utilize current APIs and remove some obsolete ones. Signed-off-by: Matias Elo <[email protected]> Reviewed-by: Janne Peltonen <[email protected]>
84b1f22
to
0e42ba1
Compare
Remove code sections copied from the API headers as they will not stay up- to-date. Update some code examples to utilize current APIs and remove some obsolete ones.