From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH 2/5] app/testpmd: remove txqflags Date: Mon, 4 Dec 2017 14:31:21 -0800 Message-ID: <176b53a6-e211-a7e4-c323-df8138505f3e@intel.com> References: <20171123120804.143897-1-shahafs@mellanox.com> <20171123120804.143897-3-shahafs@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: dev@dpdk.org To: Shahaf Shuler , jingjing.wu@intel.com Return-path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 150F7325B for ; Mon, 4 Dec 2017 23:31:23 +0100 (CET) In-Reply-To: <20171123120804.143897-3-shahafs@mellanox.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 11/23/2017 4:08 AM, Shahaf Shuler wrote: > Since testpmd is now using the new Ethdev offloads API there is no > need for the txqflags configuration. txqflag command-line option (--txqflags=0xXXXXXXXX) and command (port config all txqflags value) are way to dynamically provide Tx offload configuration to testpmd. Why you are removing them without providing equivalent feature with new offload APIs? Patch 3/4 & 4/5 adds new command-line options to enable some of recently introduced Tx offloads in testpmd, why not add a generic way to update all Tx offloads instead of those two specific offloads? Also this patch removing ability to display current Tx offload configuration.... > > Signed-off-by: Shahaf Shuler > Acked-by: Nelio Laranjeiro <...>