From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id; bh=jXwzMztAlZPHUVVmVmnt34IGzuVAPdIiSGW5DVRJysc=; b=peT5Kwg2StXhSAgxVwZGBz7Wk8XPabNXiKtuLdWmv2h51gKWWR6vf1DB7w2gjejrf9 FVdmi908Z8rVlJMeaUOGY6MeVt3MXj0wXEIwz7Z2T+fuXvHdf21ml/s0z6GKxG51QDR2 cmKZAUJqgh6KJdfVOQOw/RBphtUlEuBrn90MPt5EKd7xYiG5iIiugSfiRT3dXKzkTm7p Mhr9woEtFl2Xd476bjengJGF5eB62Br9kzycO/152JxMzKjQ41Lwi7ipW5qNaowdRmjR mEpO1meE+e27mXP1AatJzE/gOch48Cvp38hD1Skuwb4qad7MG9SYP3SY28tdGChQrKXs KOLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id; bh=jXwzMztAlZPHUVVmVmnt34IGzuVAPdIiSGW5DVRJysc=; b=WHPhkF4B9Fo3iuokxyAyob3vY8+wJfyp+2zGMO55LySdmo3AZoHnFW+DG5dUOWUxk6 SvPpV7gBpY/ya22Ap5NDVB+qwjVrr13jtlN/HKqepttPJKDv/Z1bC358mMPR1n686Wi1 QKAv71oY6Ja+Eupw23dChGg9TXDUTF9kPd3uJL/bM0fqvGGmsqQXXzB5wI4mENnJR9pk uAcbKs8NxK3Uf8MKlFT8DUPiQsS/7doPqTw0tTU/b85lXiIQRZ80M8+PPbi0qdYYILYe 4Os7IwmNj+ZBq3I7OcaidOLj+upjk3Vh9QQytzdwwtPyOCWj4JtebYf5at+0MgGpwEmd j6rw== X-Gm-Message-State: APzg51A6OeAbZJzinXr1Sv5PDSI6rfW52Fqf0XX1G0iDfqV7cS96113S Gh1g1Cs92ZGdMp9W6K6Vma4D6ssjs2NPCA== X-Google-Smtp-Source: ANB0VdYnqLY+0ijcwzAfk1K3IeKycY1gO2E1rqhj3liCh3lWGuM4dg7XRWr8EL3vyO144yXCj5cnGQ== X-Received: by 2002:a1c:2644:: with SMTP id m65-v6mr19673671wmm.155.1537369483743; Wed, 19 Sep 2018 08:04:43 -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) From: Didier Pallard To: dev@dpdk.org Date: Wed, 19 Sep 2018 17:04:05 +0200 Message-Id: <20180919150409.22880-1-didier.pallard@6wind.com> X-Mailer: git-send-email 2.11.0 Subject: [dpdk-dev] [PATCH 0/4] fix missing Tx multi segs capabilities X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Sep 2018 15:04:44 -0000 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