From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jingjing Wu <jingjing.wu@intel.com>, dev@dpdk.org
Cc: olivier.matz@6wind.com, helin.zhang@intel.com,
konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH v4 0/4] fix bitmask of supported Tx flags
Date: Wed, 8 Feb 2017 16:32:41 +0000 [thread overview]
Message-ID: <4316c677-ca2f-f98c-a3c9-b1eb14fa4123@intel.com> (raw)
In-Reply-To: <1486530353-102641-1-git-send-email-jingjing.wu@intel.com>
On 2/8/2017 5:05 AM, Jingjing Wu wrote:
> Some Tx offload flags are missed in bitmask of all supported packet
> Tx flags, it will cause rte_eth_tx_prepare fails when Tx burst packets.
>
> v4 change:
> - add PKT_TX_IEEE1588_TMST to PKT_TX_OFFLOAD_MASK
>
> v3 changes:
> - add PKT_TX_MACSEC to PKT_TX_OFFLOAD_MASK
> - refine code of drivers' TX_OFFLOAD_MASK definition
>
> v2 changes:
> - redefine the PKT_TX_OFFLOAD_MASK
> - fix more drivers
>
> Jingjing Wu (4):
> net/i40e: fix bitmask of supported Tx flags
> net/ixgbe: fix bitmask of supported Tx flags
> net/e1000: fix bitmask of supported Tx flags
Hi Jingjing,
Just to confirm, other drivers that use PKT_TX_OFFLOAD_MASK not updated
because they don't support newly added flags, right?
> mbuf: fix bitmask of Tx offload flags
>
> drivers/net/e1000/igb_rxtx.c | 8 +++++++-
> drivers/net/i40e/i40e_rxtx.c | 10 +++++++++-
> drivers/net/ixgbe/ixgbe_rxtx.c | 8 +++++++-
> lib/librte_mbuf/rte_mbuf.h | 4 +++-
> 4 files changed, 26 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2017-02-08 16:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 11:50 [dpdk-dev] [PATCH 1/2] mbuf: fix bitmask of Tx offload flags Jingjing Wu
2017-01-24 11:50 ` [dpdk-dev] [PATCH 2/2] net/i40e: fix bitmask of supported Tx flags Jingjing Wu
2017-01-26 14:19 ` [dpdk-dev] [PATCH 1/2] mbuf: fix bitmask of Tx offload flags Ferruh Yigit
2017-02-04 3:36 ` [dpdk-dev] [PATCH v2 0/5] fix bitmask of supported Tx flags Jingjing Wu
2017-02-04 3:36 ` [dpdk-dev] [PATCH v2 1/5] mbuf: fix bitmask of Tx offload flags Jingjing Wu
2017-02-04 3:36 ` [dpdk-dev] [PATCH v2 2/5] net/i40e: fix bitmask of supported Tx flags Jingjing Wu
2017-02-05 10:28 ` Ferruh Yigit
2017-02-06 3:02 ` Wu, Jingjing
2017-02-06 10:28 ` Olivier Matz
2017-02-07 2:30 ` Wu, Jingjing
2017-02-06 10:26 ` Olivier Matz
2017-02-07 2:30 ` Wu, Jingjing
2017-02-04 3:36 ` [dpdk-dev] [PATCH v2 3/5] net/ixgbe: " Jingjing Wu
2017-02-05 11:59 ` Ananyev, Konstantin
2017-02-05 12:10 ` Ananyev, Konstantin
2017-02-06 8:53 ` Wu, Jingjing
2017-02-06 12:11 ` Ananyev, Konstantin
2017-02-07 2:29 ` Wu, Jingjing
2017-02-08 0:34 ` Ananyev, Konstantin
2017-02-04 3:36 ` [dpdk-dev] [PATCH v2 4/5] net/e1000: " Jingjing Wu
2017-02-04 3:36 ` [dpdk-dev] [PATCH v2 5/5] net/fm10k: " Jingjing Wu
2017-02-07 3:22 ` [dpdk-dev] [PATCH v3 0/4] " Jingjing Wu
2017-02-07 3:22 ` [dpdk-dev] [PATCH v3 1/4] net/i40e: " Jingjing Wu
2017-02-07 13:48 ` Ferruh Yigit
2017-02-07 15:45 ` Wu, Jingjing
2017-02-07 16:01 ` Ferruh Yigit
2017-02-07 3:22 ` [dpdk-dev] [PATCH v3 2/4] net/ixgbe: " Jingjing Wu
2017-02-07 3:22 ` [dpdk-dev] [PATCH v3 3/4] net/e1000: " Jingjing Wu
2017-02-07 3:22 ` [dpdk-dev] [PATCH v3 4/4] mbuf: fix bitmask of Tx offload flags Jingjing Wu
2017-02-08 5:05 ` [dpdk-dev] [PATCH v4 0/4] fix bitmask of supported Tx flags Jingjing Wu
2017-02-08 5:05 ` [dpdk-dev] [PATCH v4 1/4] net/i40e: " Jingjing Wu
2017-02-08 5:05 ` [dpdk-dev] [PATCH v4 2/4] net/ixgbe: " Jingjing Wu
2017-02-08 5:05 ` [dpdk-dev] [PATCH v4 3/4] net/e1000: " Jingjing Wu
2017-02-08 5:05 ` [dpdk-dev] [PATCH v4 4/4] mbuf: fix bitmask of Tx offload flags Jingjing Wu
2017-02-08 16:27 ` Olivier MATZ
2017-02-08 16:32 ` Ferruh Yigit [this message]
2017-02-09 1:13 ` [dpdk-dev] [PATCH v4 0/4] fix bitmask of supported Tx flags Wu, Jingjing
2017-02-08 16:46 ` Ananyev, Konstantin
2017-02-09 14:37 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4316c677-ca2f-f98c-a3c9-b1eb14fa4123@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).