From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <konstantin.ananyev@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 46DBE10D6D
 for <dev@dpdk.org>; Thu, 22 Dec 2016 15:11:36 +0100 (CET)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by orsmga101.jf.intel.com with ESMTP; 22 Dec 2016 06:11:35 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,388,1477983600"; d="scan'208";a="801283417"
Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25])
 by FMSMGA003.fm.intel.com with ESMTP; 22 Dec 2016 06:11:34 -0800
Received: from irsmsx105.ger.corp.intel.com ([169.254.7.212]) by
 irsmsx110.ger.corp.intel.com ([169.254.15.101]) with mapi id 14.03.0248.002;
 Thu, 22 Dec 2016 14:11:33 +0000
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
CC: "Kulasek, TomaszX" <tomaszx.kulasek@intel.com>, Olivier Matz
 <olivier.matz@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>
Thread-Topic: [dpdk-dev] [PATCH v12 1/6] ethdev: add Tx preparation
Thread-Index: AQHSRbBXtZ+k3KL6/UOfLLeqKZ5NC6DzVKAAgACPLdCAAHvNgIAAf21AgAmFZoCAAZDxAIAESfRggA/kdwCAAAobwA==
Date: Thu, 22 Dec 2016 14:11:32 +0000
Message-ID: <2601191342CEEE43887BDE71AB9772583F0F3FAD@irsmsx105.ger.corp.intel.com>
References: <1477486575-25148-1-git-send-email-tomaszx.kulasek@intel.com>
 <3042915272161B4EB253DA4D77EB373A14F5A409@IRSMSX102.ger.corp.intel.com>
 <2601191342CEEE43887BDE71AB9772583F0E689E@irsmsx105.ger.corp.intel.com>
 <2376458.ueV7yndzPH@xps13>
In-Reply-To: <2376458.ueV7yndzPH@xps13>
Accept-Language: en-IE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.181]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [PATCH v12 1/6] ethdev: add Tx preparation
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Thu, 22 Dec 2016 14:11:37 -0000

>=20
> 2016-12-12 11:51, Ananyev, Konstantin:
> > > > The application gets few information from tx_prepare() about what s=
hould
> > > > 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 erro=
r information,
> > OR something else?
>=20
> 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?

I think that's the good reason and I am ok with it.=20
Konstantin