From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH 0/6] get status of Rx and Tx descriptors
Date: Mon, 06 Mar 2017 11:41:53 +0100
Message-ID: <1589082.r4f9rZvk63@xps13>
References: <1479981261-19512-1-git-send-email-olivier.matz@6wind.com>
 <20170301100706.5df566fb@xeon-e3> <20170302144326.7d65fc39@platinum>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org,
 konstantin.ananyev@intel.com, wenzhuo.lu@intel.com, helin.zhang@intel.com,
 jingjing.wu@intel.com, adrien.mazarguil@6wind.com, nelio.laranjeiro@6wind.com,
 ferruh.yigit@intel.com, bruce.richardson@intel.com
To: Olivier Matz <olivier.matz@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50])
 by dpdk.org (Postfix) with ESMTP id E2465591E
 for <dev@dpdk.org>; Mon,  6 Mar 2017 11:41:54 +0100 (CET)
Received: by mail-wm0-f50.google.com with SMTP id v186so60241559wmd.0
 for <dev@dpdk.org>; Mon, 06 Mar 2017 02:41:54 -0800 (PST)
In-Reply-To: <20170302144326.7d65fc39@platinum>
List-Id: DPDK patches and discussions <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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2017-03-02 14:43, Olivier Matz:
> Hi Stephen,
> 
> On Wed, 1 Mar 2017 10:07:06 -0800, Stephen Hemminger <stephen@networkplumber.org> wrote:
> > On Wed,  1 Mar 2017 18:19:06 +0100
> > Olivier Matz <olivier.matz@6wind.com> wrote:
> > 
> > > This patchset introduces a new ethdev API:
> > > - rte_eth_rx_descriptor_status()
> > > - rte_eth_tx_descriptor_status()
[...]
> > Could you update examples to use this?
> 
> I can update examples/l3fwd-power, but it will break the
> support for drivers that do not implement the new API. Maybe we could
> do this in a second time, after all drivers are converted?

Yes, good idea