From: Alexander Duyck <alexander.h.duyck@intel.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [net-next-2.6 PATCH 2/2] ethtool: add ntuple flow specifier data to network flow classifier
Date: Fri, 08 Apr 2011 15:35:42 -0700 [thread overview]
Message-ID: <4D9F8DBE.2050503@intel.com> (raw)
In-Reply-To: <1302301284.2871.25.camel@bwh-desktop>
On 4/8/2011 3:21 PM, Ben Hutchings wrote:
> On Fri, 2011-04-08 at 15:07 -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.
>
> Thanks for carrying on with this.
>
> [...]
>> /**
>> * 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.
>> * @ring_cookie: RX ring/queue index to deliver to, or %RX_CLS_FLOW_DISC
>> * if packets should be discarded
>> * @location: Index of filter in hardware table
>> */
>> struct ethtool_rx_flow_spec {
>> __u32 flow_type;
>> - union {
>> - struct ethtool_tcpip4_spec tcp_ip4_spec;
>> - struct ethtool_tcpip4_spec udp_ip4_spec;
>> - struct ethtool_tcpip4_spec sctp_ip4_spec;
>> - struct ethtool_ah_espip4_spec ah_ip4_spec;
>> - struct ethtool_ah_espip4_spec esp_ip4_spec;
>> - struct ethtool_usrip4_spec usr_ip4_spec;
>> - struct ethhdr ether_spec;
>> - __u8 hdata[72];
>> - } h_u, m_u;
>> + union ethtool_flow_union h_u;
>> + struct ethtool_flow_ext h_ext;
>> + union ethtool_flow_union m_u;
>> + struct ethtool_flow_ext m_ext;
>> + __u32 flow_type_ext;
> [...]
>
> You can't add flow_type_ext here. I assume this is an oversight, since
> it isn't mentioned anywhere else.
>
> Ben.
>
Yeah, I forgot and left it in there. It will be removed and resubmitted.
Thanks,
Alex
prev parent reply other threads:[~2011-04-08 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 22:07 [net-next-2.6 PATCH 0/2] Start of work to cleanup ntuple filters Alexander Duyck
2011-04-08 22:07 ` [net-next-2.6 PATCH 1/2] ethtool: prevent null pointer dereference with NTUPLE set but no set_rx_ntuple Alexander Duyck
2011-04-11 20:21 ` David Miller
2011-04-08 22:07 ` [net-next-2.6 PATCH 2/2] ethtool: add ntuple flow specifier data to network flow classifier Alexander Duyck
2011-04-08 22:21 ` Ben Hutchings
2011-04-08 22:35 ` Alexander Duyck [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=4D9F8DBE.2050503@intel.com \
--to=alexander.h.duyck@intel.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
/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).