DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: remove tpid check for fdir filter
Date: Fri, 14 Apr 2017 01:37:12 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA0207EAD7@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <2866c3e3-bc04-f919-f533-23dc38bafbc7@intel.com>

Hi, Ferruh

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Thursday, April 13, 2017 6:21 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: remove tpid check for fdir filter
> 
> On 4/13/2017 8:49 AM, Wei Zhao wrote:
> > DPDK community has several emails discussion on this topic, these
> > mails name is "FW: Issues with ixgbe and rte_flow",
> 
> Can you please add reference to discussions by mail list archive links.
> Like: http://dpdk.org/ml/archives/dev/2017-April/063942.html
> 

I have got it,  I will fix that in v2

> > items like VLAN can already have several valid "types"
> > (0x88a8, 0x8100, 0x9100), and who knows what will come up in the
> > future.And ixgbe_flow just ignores the types when do filter
> > configuration. So it may be reasonable to delete the related tpid
> > check process.
> > Also add some more comment log on stack explanation.
> >
> > Fixes: 11777435c72 ("net/ixgbe: parse flow director filter")
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> 
> <...>



  reply	other threads:[~2017-04-14  1:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  7:49 Wei Zhao
2017-04-13 10:21 ` Ferruh Yigit
2017-04-14  1:37   ` Zhao1, Wei [this message]
2017-04-14  3:34 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2017-04-14  9:17   ` 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=A2573D2ACFCADC41BB3BE09C6DE313CA0207EAD7@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).