[dpdk-dev] Ethernet API - multiple post-RX-burst callbacks' run-order is opposite to their add-order
Thomas Monjalon
thomas.monjalon at 6wind.com
Fri Jul 10 15:24:28 CEST 2015
2015-07-10 13:14, Mcnamara, John:
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Sanford, Robert
> > When one adds multiple post-RX-burst callbacks to a queue, their execution
> > order is the opposite of the order in which they are added.
>
> Hi,
>
> I think you are right and that the current order of execution for callbacks is counter-intuitive.
>
> I've submitted a patch to fix the order:
>
> http://dpdk.org/dev/patchwork/patch/6300/
Thanks John.
Don't hesitate to use Suggested-by: to give credits.
> If the patch is accepted I'll add a note to the release notes also.
Why not doing the release notes change atomicly in the same patch?
More information about the dev
mailing list