From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH v12 1/6] ethdev: add Tx preparation
Date: Thu, 22 Dec 2016 14:30:38 +0100
Message-ID: <2376458.ueV7yndzPH@xps13>
References: <1477486575-25148-1-git-send-email-tomaszx.kulasek@intel.com>
 <3042915272161B4EB253DA4D77EB373A14F5A409@IRSMSX102.ger.corp.intel.com>
 <2601191342CEEE43887BDE71AB9772583F0E689E@irsmsx105.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: "Kulasek, TomaszX" <tomaszx.kulasek@intel.com>,
 Olivier Matz <olivier.matz@6wind.com>, dev@dpdk.org
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wj0-f172.google.com (mail-wj0-f172.google.com
 [209.85.210.172]) by dpdk.org (Postfix) with ESMTP id 6363510D59
 for <dev@dpdk.org>; Thu, 22 Dec 2016 14:30:40 +0100 (CET)
Received: by mail-wj0-f172.google.com with SMTP id ez4so10419723wjd.0
 for <dev@dpdk.org>; Thu, 22 Dec 2016 05:30:40 -0800 (PST)
In-Reply-To: <2601191342CEEE43887BDE71AB9772583F0E689E@irsmsx105.ger.corp.intel.com>
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>

2016-12-12 11:51, Ananyev, Konstantin:
> > > The application gets few information from tx_prepare() about what should
> > > be done to make the packet accepted by the hw, and the actions will
> > > probably be different depending on hardware.
> 
> That's true.
> I am open to suggestions how in future to provide extra information to the upper layer.
> Set rte_errno to different values depending on type of error,
> OR extra parameter in tx_prepare() that will provide more detailed error information,
> OR something else?

That's one of the reason which give me a feeling that it is safer
to introduce tx_prepare as an experimental API in 17.02.
So the users will know that it can change in the next release.
What do you think?