From: Didier Pallard Subject: [PATCH 0/4] fix missing Tx multi segs capabilities Date: Wed, 19 Sep 2018 17:04:05 +0200 Message-ID: <20180919150409.22880-1-didier.pallard@6wind.com> To: dev@dpdk.org Return-path: Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) by dpdk.org (Postfix) with ESMTP id 4D66E1041 for ; Wed, 19 Sep 2018 17:04:44 +0200 (CEST) Received: by mail-wm1-f65.google.com with SMTP id s12-v6so6669034wmc.0 for ; Wed, 19 Sep 2018 08:04:44 -0700 (PDT) Received: from pala.dev.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id z21-v6sm3572751wmi.29.2018.09.19.08.04.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Sep 2018 08:04:43 -0700 (PDT) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating that application will never send multisegmented packets, allowing pmd to choose different tx methods accordingly. In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability that is advertised by pmds, some of them do not advertise it and expect to never receive fragmented packets (octeontx, axgbe) So an ethdev that supports multisegmented packets should properly advertise it. Didier Pallard (4): net/e1000: fix missing Tx multi segs capability net/fm10k: fix missing Tx multi segs capability net/i40e: fix missing Tx multi segs capability net/ixgbe: fix missing Tx multi segs capability drivers/net/e1000/em_rxtx.c | 1 + drivers/net/fm10k/fm10k_ethdev.c | 1 + drivers/net/i40e/i40e_vf_representor.c | 1 + drivers/net/ixgbe/ixgbe_vf_representor.c | 2 +- 4 files changed, 4 insertions(+), 1 deletion(-) -- 2.11.0