From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Ethernet API - multiple post-RX-burst callbacks' run-order is opposite to their add-order Date: Fri, 10 Jul 2015 15:24:28 +0200 Message-ID: <5006330.bOZQCtd0U5@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Mcnamara, John" Return-path: Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 9D39D5FEB for ; Fri, 10 Jul 2015 15:25:36 +0200 (CEST) Received: by wgxm20 with SMTP id m20so66054612wgx.3 for ; Fri, 10 Jul 2015 06:25:36 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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?