From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Ethernet API - multiple post-RX-burst callbacks' run-order is opposite to their add-order
Date: Fri, 10 Jul 2015 15:24:28 +0200 [thread overview]
Message-ID: <5006330.bOZQCtd0U5@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2F6A381@IRSMSX103.ger.corp.intel.com>
2015-07-10 13:14, Mcnamara, John:
> From: dev [mailto:dev-bounces@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?
next prev parent reply other threads:[~2015-07-10 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 21:04 Sanford, Robert
2015-07-03 9:57 ` Bruce Richardson
2015-07-03 10:02 ` Thomas Monjalon
2015-07-10 13:14 ` Mcnamara, John
2015-07-10 13:24 ` Thomas Monjalon [this message]
2015-07-10 13:52 ` Mcnamara, John
2015-07-10 14:02 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5006330.bOZQCtd0U5@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).