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 v2] net/ixgbe: fix ntuple filter support for sctp
Date: Fri, 28 Apr 2017 02:18:01 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA0208160C@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <4b2ef680-c9b7-6358-c3b7-f60b9b204585@intel.com>

Hi,Ferruh

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Thursday, April 27, 2017 5:44 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbe: fix ntuple filter support for
> sctp
> 
> On 4/27/2017 6:39 AM, Wei Zhao wrote:
> > Add the support of RTE_FLOW_ITEM_TYPE_SCTP type packet for ixgbe
> > ntuple filter.
> >
> > v2:
> > --add type check of RTE_FLOW_ITEM_TYPE_SCTP for item flow.
> 
> For version information in the commit log, can you put it as:
> Below signed-off tag, in new line put three dashes "---", later put the version
> information. This way git automatically strips that part when applied,
> otherwise maintainer manually needs to do the update.
> 

Ok, fix in v3

> And can you please send new version of the patches using git send-email "--
> in-reply-to" option, otherwise it is hard to trace the patch versions and
> previous comments on it.
> 

Sorry, I have forget that info.

> Thanks.
> 
> >
> > Fixes: 672be56d76a ("net/ixgbe: parse n-tuple filter")
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> > ---
> >  drivers/net/ixgbe/ixgbe_flow.c | 30 ++++++++++++++++++++++++++++--
> >  1 file changed, 28 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/ixgbe/ixgbe_flow.c
> > b/drivers/net/ixgbe/ixgbe_flow.c index e2ba9c2..98e414a 100644
> > --- a/drivers/net/ixgbe/ixgbe_flow.c
> > +++ b/drivers/net/ixgbe/ixgbe_flow.c
> > @@ -142,6 +142,8 @@ cons_parse_ntuple_filter(const struct rte_flow_attr
> *attr,
> >  	const struct rte_flow_item_tcp *tcp_mask;
> >  	const struct rte_flow_item_udp *udp_spec;
> >  	const struct rte_flow_item_udp *udp_mask;
> > +	const struct rte_flow_item_sctp *sctp_spec;
> > +	const struct rte_flow_item_sctp *sctp_mask;
> >  	uint32_t index;
> >
> >  	if (!pattern) {
> > @@ -253,7 +255,8 @@ cons_parse_ntuple_filter(const struct rte_flow_attr
> *attr,
> >  	index++;
> >  	NEXT_ITEM_OF_PATTERN(item, pattern, index);
> >  	if (item->type != RTE_FLOW_ITEM_TYPE_TCP &&
> > -	    item->type != RTE_FLOW_ITEM_TYPE_UDP) {
> > +	    item->type != RTE_FLOW_ITEM_TYPE_UDP &&
> > +	    item->type != RTE_FLOW_ITEM_TYPE_SCTP) {
> 
> There is a function comment, that documents the expected/valid pattern
> types, that should be updated with this new type.

Ok, I will fix that in v3.

  reply	other threads:[~2017-04-28  2:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27  5:39 Wei Zhao
2017-04-27  7:12 ` Lu, Wenzhuo
2017-04-27  9:43 ` Ferruh Yigit
2017-04-28  2:18   ` Zhao1, Wei [this message]
2017-04-28  3:37 ` [dpdk-dev] [PATCH v3] " Wei Zhao
2017-04-28  5:36   ` Ferruh Yigit
2017-04-28  3:40 ` Wei Zhao
  -- strict thread matches above, loose matches on Subject: below --
2017-04-27  5:37 [dpdk-dev] [PATCH v2] " Wei Zhao

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=A2573D2ACFCADC41BB3BE09C6DE313CA0208160C@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).