DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Didier Pallard <didier.pallard@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Ye, Xiaolong" <xiaolong.ye@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/i40e: revert fix offload not supported mask
Date: Wed, 12 Dec 2018 03:03:56 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611532FD2A3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <38c25e0c-1c7f-389c-16bd-14cd56789bae@intel.com>



> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Wednesday, December 12, 2018 6:01 AM
> To: Didier Pallard <didier.pallard@6wind.com>; dev@dpdk.org
> Cc: stable@dpdk.org; Ye, Xiaolong <xiaolong.ye@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Subject: Re: [dpdk-stable] [PATCH] net/i40e: revert fix offload not supported
> mask
> 
> On 12/11/2018 5:25 PM, Didier Pallard wrote:
> > This reverts
> > commit 09a62d75691f ("net/i40e: fix offload not supported mask")
> >
> > Contrary to what is said in above patch commit log,
> > I40E_TX_OFFLOAD_NOTSUP_MASK is the mask of Tx offload bits that are
> > part of PKT_TX_OFFLOAD_MASK but not included in I40E_TX_OFFLOAD_MASK.
> > Above patch erroneously includes all PKT_RX_OFFLOAD_ bits in the
> > I40E_TX_OFFLOAD_NOTSUP_MASK, this is not what is expected.
> 
> Argh, yes it does set Rx offload bits, +1 to revert.
> cc'ed author and maintainers of the PMD.

I think this revert make sense to me, I didn't notice Tx offload and Rx offload shared the same 64 bits previously 

> 
> > Restore the initial xor that gives the expected result.
> >
> > Fixes: 09a62d75691f ("net/i40e: fix offload not supported mask")
> > Cc: stable@dpdk.org
> > Signed-off-by: Didier Pallard <didier.pallard@6wind.com>
> > ---
> >  drivers/net/i40e/i40e_rxtx.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/i40e/i40e_rxtx.c
> > b/drivers/net/i40e/i40e_rxtx.c index e1152ff0ea58..ab74a488f88b 100644
> > --- a/drivers/net/i40e/i40e_rxtx.c
> > +++ b/drivers/net/i40e/i40e_rxtx.c
> > @@ -69,7 +69,7 @@
> >  		I40E_TX_IEEE1588_TMST)
> >
> >  #define I40E_TX_OFFLOAD_NOTSUP_MASK \
> > -		~(PKT_TX_OFFLOAD_MASK & I40E_TX_OFFLOAD_MASK)
> > +		(PKT_TX_OFFLOAD_MASK ^ I40E_TX_OFFLOAD_MASK)
> >
> >  static inline void
> >  i40e_rxd_to_vlan_tci(struct rte_mbuf *mb, volatile union i40e_rx_desc
> > *rxdp)
> >


  reply	other threads:[~2018-12-12  3:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 17:25 [dpdk-dev] " Didier Pallard
2018-12-11 22:01 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2018-12-12  3:03   ` Zhang, Qi Z [this message]
2018-12-12  6:17   ` Ye Xiaolong
2018-12-13  9:47 ` [dpdk-dev] " Zhang, Qi Z

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=039ED4275CED7440929022BC67E70611532FD2A3@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=didier.pallard@6wind.com \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.org \
    --cc=xiaolong.ye@intel.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).