Skip to content
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

Scheduler classifier and LAGs in ODP #1000

Open
Neetika02 opened this issue Jul 17, 2020 · 1 comment
Open

Scheduler classifier and LAGs in ODP #1000

Neetika02 opened this issue Jul 17, 2020 · 1 comment

Comments

@Neetika02
Copy link

Hello,

I have following unrelated queries:

  • Does ODP Support Link Aggregate Groups. If yes how?

  • When using Scheduler/Classifier API over DPDK how do we know if the flow matching is being done at Hardware or Software. Is this a compile time option or can I check this using capability query?

Regards,
Neetika

@JannePeltonen
Copy link
Collaborator

ODP API does not directly support link aggregation but allows the application to implement it in SW on top of the ODP API. In addition, ODP API does not preclude an ODP implementation from exposing a group of aggregated ports as single pktio, but in this case the configuration and management of the aggregation would not be done through ODP API.

If you use DPDK for packet I/O within the ODP implementation, you may be able to use the DPDK link bonding PMD and have it visible as single ODP pktio in the ODP API. I have not tried it so I do not know if making it work requires some tweaking.

The extent of HW offloading varies across ODP implementations and in general ODP API does not tell whether something is HW or SW based but considers it an implementation detail (there are some exceptions to this in the ODP crypto API). Linux generic ODP and odp-dpdk implement packet classification in SW.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants