DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "Xing, Beilei" <beilei.xing@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] net/i40e: fix parsing QinQ packets type issue
Date: Fri, 23 Sep 2016 12:00:51 +0100	[thread overview]
Message-ID: <20160923110050.GB58488@bricha3-MOBL3> (raw)
In-Reply-To: <9BB6961774997848B5B42BEC655768F80E2713A8@SHSMSX103.ccr.corp.intel.com>

On Thu, Sep 22, 2016 at 07:40:20AM +0000, Wu, Jingjing wrote:
> 
> 
> > -----Original Message-----
> > From: Xing, Beilei
> > Sent: Monday, September 12, 2016 5:42 PM
> > To: Wu, Jingjing
> > Cc: dev@dpdk.org; Xing, Beilei
> > Subject: [PATCH v3] net/i40e: fix parsing QinQ packets type issue
> > 
> > Previously, PTYPE filed in the RX descriptors is not set properly for QinQ
> > packets, wrong PTYPE is generated because outer Tag did not have ORT/PIT
> > configured. Fix this issue by configuring ORT/PIT.
> > Otherwise, this patch changes bitmask of outer VLAN tag in L2 header to
> > support RSS and flow director for QinQ.
> > 
> > Fixes: 4861cde46116 ("i40e: new poll mode driver")
> > Fixes: 4072d503aaa5 ("i40e: fix VLAN bitmasks for input set")
> > 
> > Signed-off-by: Beilei Xing <beilei.xing@intel.com>
> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
> 
Applied to dpdk-next-net/rel_16_11

/Bruce

      reply	other threads:[~2016-09-23 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  3:20 [dpdk-dev] [PATCH] " Beilei Xing
2016-08-21  1:21 ` Wu, Jingjing
2016-08-23  9:44 ` [dpdk-dev] [PATCH v2] " Beilei Xing
2016-09-05  5:36   ` Wu, Jingjing
2016-09-12  9:41   ` [dpdk-dev] [PATCH v3] " Beilei Xing
2016-09-22  7:40     ` Wu, Jingjing
2016-09-23 11:00       ` Bruce Richardson [this message]

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=20160923110050.GB58488@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@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).