[dpdk-dev] Ethernet API - multiple post-RX-burst callbacks' run-order is opposite to their add-order

Mcnamara, John john.mcnamara at intel.com
Fri Jul 10 15:14:41 CEST 2015


> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Sanford, Robert
> Sent: Thursday, July 2, 2015 10:05 PM
> To: Richardson, Bruce; Thomas Monjalon; dev at dpdk.org
> Subject: [dpdk-dev] Ethernet API - multiple post-RX-burst callbacks' run-
> order is opposite to their add-order
> 
> 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/

If the patch is accepted I'll add a note to the release notes also.

John.
-- 



More information about the dev mailing list