[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1302324249.15899.23.camel@ahduyck-mobl2.amr.corp.intel.com>
Date: Fri, 08 Apr 2011 21:44:09 -0700
From: Alexander H Duyck <alexander.h.duyck@...el.com>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: "davem@...emloft.net" <davem@...emloft.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Santwona Behera <santwona.behera@....com>
Subject: Re: [net-next-2.6 PATCH] v2 ethtool: add ntuple flow specifier
data to network flow classifier
On Fri, 2011-04-08 at 17:13 -0700, Ben Hutchings wrote:
> On Fri, 2011-04-08 at 15:34 -0700, Alexander Duyck wrote:
> > This change is meant to add an ntuple data extensions to the rx network flow
> > classification specifiers. The idea is to allow ntuple to be displayed via
> > the network flow classification interface.
> [...]
> > /**
> > * struct ethtool_rx_flow_spec - specification for RX flow filter
> > * @flow_type: Type of match to perform, e.g. %TCP_V4_FLOW
> > * @h_u: Flow fields to match (dependent on @flow_type)
> > + * @h_ext: Additional fields to match
> > * @m_u: Masks for flow field bits to be ignored
> > + * @m_ext: Masks for additional field bits to be ignored.
> > + * Note, all additional fields must be ignored unless @flow_type
> > + * includes the %FLOW_EXT flag.
> [...]
>
> Sorry I didn't bring this up against v1:
>
> I think you worked out that these masks are interpreted as bits to be
> matched, rather than bits to be ignored, in the existing implementation
> in niu. Looking again at niu, I think that you were right about that.
> So please fix the comment while you're updating it.
>
> Ben.
>
I completely forgot all about that. Thanks for catching it.
v3 is updated and submitted.
Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists