Hi Gyanesh,
Have you had a chance to look at
https://bugs.linaro.org/show_bug.cgi?id=3657 and see if Matias' suggestions
are helpful to you?
Thanks,
Regards,
Bill
https://bugs.linaro.org/show_bug.cgi?id=3675
Bill Fischofer changed:
What|Removed |Added
Resolution|--- |FIXED
Branch: refs/heads/master
Home: https://github.com/Linaro/odp
Commit: 4aacfd4d72b80a22d449d865a6c4f063afa823ab
https://github.com/Linaro/odp/commit/4aacfd4d72b80a22d449d865a6c4f063afa823ab
Author: Petri Savolainen
Date: 2018-03-26 (Mon, 26 Mar
https://bugs.linaro.org/show_bug.cgi?id=3688
--- Comment #5 from Bogdan Pricope ---
I mean, you can use queue context to associate with an input/intermediary queue
a specific output queue so you can keep order on output.
--
You are receiving this mail because:
You
https://bugs.linaro.org/show_bug.cgi?id=3688
--- Comment #4 from Janne Peltonen ---
Atomic input queues in l2fwd guarantee that packets of the same flow are passed
to odp_pktout_send() or odp_queue_enq_multi() in the correct order. This is
because only single thread can
https://bugs.linaro.org/show_bug.cgi?id=3688
--- Comment #3 from Bogdan Pricope ---
/**
* @def ODP_SCHED_SYNC_ORDERED
* Ordered queue synchronization
*
* Events from an ordered queue can be scheduled to multiple threads for
* concurrent processing but still
https://bugs.linaro.org/show_bug.cgi?id=3688
--- Comment #2 from Bogdan Pricope ---
Hi BIll, Janne,
My knowledge on "odp scheduling" internals are limited, yet I can comment on
API:
* @def ODP_SCHED_SYNC_ATOMIC
* Atomic queue synchronization
*
* Events from an
https://bugs.linaro.org/show_bug.cgi?id=3688
Bill Fischofer changed:
What|Removed |Added
Assignee|maxim.uva...@linaro.org
https://bugs.linaro.org/show_bug.cgi?id=3688
Bug ID: 3688
Summary: l2fwd example does not preserve packet order
Product: OpenDataPlane - linux- generic reference
Version: master
Hardware: x86
OS: Linux
Status: