From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id CDA877D5E
 for <dev@dpdk.org>; Thu, 24 Aug 2017 00:16:25 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 2CA23210A5;
 Wed, 23 Aug 2017 18:16:25 -0400 (EDT)
Received: from frontend2 ([10.202.2.161])
 by compute1.internal (MEProxy); Wed, 23 Aug 2017 18:16:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=TcmlGkwW6/LTTOw
 2cZQbuuhOcUnBHlTWabIVKYrJXiU=; b=cdMSBpLocsybKfoL4ZEYhY7WFCmXQCE
 W5K/7QT3V1DiZwZz38iWM5E7XX3YJtCkC2nXqO4P1xJF3yCilvW0ho10u+JS3ra0
 wo92nmkiGpZKnhs3Q8mzVCXe8GgBOPzKqTabjArBHmanHgdBQ+/vOpJw4SGeM2Wv
 siue1s8GiYLo=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=
 fm1; bh=TcmlGkwW6/LTTOw2cZQbuuhOcUnBHlTWabIVKYrJXiU=; b=dG9Nfy9g
 r1YTu1fxvp+4PfalyG78SDisAUVntO4PCOLGs3wQQPN2jmJNDuTAgFOdc4TKR6u+
 eSKzYf6TNEBh+2Gup8QjOftFzhgnkFeJk8fyudk5As03gkmmzhqr2d7rCdgGdWbc
 YWgm8ur/SAIWKFm6OdLDnRUmBHglJk+P5S/80GZkm+n0cMP4O9kemfua0OOv0BEC
 mQwic0mx55DrdLCBVai4pzS0+nyN9YxXd7NJBjnHtZTCuhOXflgmNUXybLirm2WM
 IQwNsUyrGpE2B2iqVeM8QpS9Sp1ix69yPDNgdJfps3vvkHsLnwtMRGwWvgk4CSgT
 S1GSZXUDytGxIA==
X-ME-Sender: <xms:uf6dWUb1NN2ab8MRgvOkyfbHUHGeUYTQspS6KMxIpNe6QO3bYp-Y4A>
X-Sasl-enc: OgwvvmKb1al+5blJMdZl8I0CLduRTlo0MsoH+t5UNL3g 1503526584
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id D2291249CD;
 Wed, 23 Aug 2017 18:16:24 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: dev@dpdk.org, Jerin Jacob <jerin.jacob@cavium.com>
Date: Thu, 24 Aug 2017 00:16:23 +0200
Message-ID: <3508090.iDIxO5zDVA@xps>
In-Reply-To: <cover.1502096064.git.shahafs@mellanox.com>
References: <cover.1502096064.git.shahafs@mellanox.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [RFC PATCH 0/4] ethdev new offloads API
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: Wed, 23 Aug 2017 22:16:26 -0000

07/08/2017 12:54, Shahaf Shuler:
> The new API does not have an equivalent for the below Tx flags:
> 
> * ETH_TXQ_FLAGS_NOREFCOUNT
> * ETH_TXQ_FLAGS_NOMULTMEMP
> 
> The reason is that those flags are not to manage offloads, rather some
> guarantee from application on the way it uses mbufs, therefore could not be
> present as part of DEV_TX_OFFLOADS_*.
> Such flags are useful only for benchmarks, and therefore provide a non-realistic    
> performance for DPDK customers using simple benchmarks for evaluation.
> Leveraging the work being done in this series to clean up those flags.

I agree that these flags are not offload but benchmark configuration.
They should be deprecated.