From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
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 <dev@dpdk.org>; Fri, 10 Jul 2015 15:25:36 +0200 (CEST)
Received: by wgxm20 with SMTP id m20so66054612wgx.3
 for <dev@dpdk.org>; Fri, 10 Jul 2015 06:25:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=r7Ys776Q1X9aMxy/sJeujx6cBlyk20mmWbYiwa/9tkI=;
 b=bpd+r+WNE6gqwoUXoaODgVH8sibG+ypLxFXAlMGwUw257PHkJtvYu7mMuCBN7aGTxt
 pi0i+2+3Zq68f6HUwH5Q9hwU9g4jdTFFERKBfNak4msfhtqXR6I8Jn2t7cilHKkvL3mr
 MC/AJ9jQbE/yiauqbDsvJ1o0PRI0oJhC5i/VOQ/x0fECd7kb1wIhraZWZA+XMfuvLxav
 iEEZGJUb+gGtsv4lg9sG8Z6VOrOWFUm0f57FO0ktJzE7oz0IGIs0Pac9NBLU/x9qtADH
 eE+tL66jWXDu/a91hYIbnRsWPHxIteLbTBpsEUd+s7BHVWQJUXhAIqmmRaN9yUy3GpTj
 ltLw==
X-Gm-Message-State: ALoCoQkom35JE/R5WM1FNPhYMXlCYMh1NDclz9tztVyusvazhNHDFBUS/63Sc11EaVZqWfczdvtS
X-Received: by 10.194.48.108 with SMTP id k12mr43037366wjn.151.1436534736482; 
 Fri, 10 Jul 2015 06:25:36 -0700 (PDT)
Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136])
 by smtp.gmail.com with ESMTPSA id js3sm13647399wjc.5.2015.07.10.06.25.35
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Fri, 10 Jul 2015 06:25:35 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Date: Fri, 10 Jul 2015 15:24:28 +0200
Message-ID: <5006330.bOZQCtd0U5@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; )
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2F6A381@IRSMSX103.ger.corp.intel.com>
References: <D1BB0052.A7DB%rsanford@akamai.com>
 <B27915DBBA3421428155699D51E4CFE2F6A381@IRSMSX103.ger.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Ethernet API - multiple post-RX-burst callbacks'
	run-order is opposite to their add-order
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2015 13:25:36 -0000

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?