From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: RFC: ethtool support for n-tuple filter programming
Date: Sun, 08 Nov 2009 22:54:18 -0800 [thread overview]
Message-ID: <1257749659.2609.6.camel@ppwaskie-mobl2> (raw)
In-Reply-To: <20091108.223848.234795788.davem@davemloft.net>
On Sun, 2009-11-08 at 23:38 -0700, David Miller wrote:
> From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
> Date: Sun, 08 Nov 2009 21:49:21 -0800
>
> > On Sat, 2009-11-07 at 21:27 -0700, David Miller wrote:
> >> From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
> >> Date: Fri, 06 Nov 2009 10:57:21 -0800
> >>
> >> > Any comments, thoughts, suggestions, or ideas are welcome.
> >>
> >> We can use the existing datastructures and defines used for
> >> ETHTOOL_GRX* for new ethtool commands that do filtering.
> >>
> >> NIU can filter on these tuples too.
> >
> > Are you suggesting to extend the flow hash stuff that is already in
> > ethtool (same ioctl)? If so, that makes sense. I'll go ahead and get
> > some patches together for review.
>
> Not exactly.
>
> Rather, I'm saying to use a new ethtool command, but make use of the
> existing flow hash datastructures as much as possible.
Ah ok. Makes even more sense.
Thanks David.
-PJ
prev parent reply other threads:[~2009-11-09 6:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 18:57 RFC: ethtool support for n-tuple filter programming Peter P Waskiewicz Jr
2009-11-06 19:12 ` Caitlin Bestler
2009-11-06 19:31 ` Peter P Waskiewicz Jr
2009-11-07 19:49 ` Bill Fink
2009-11-07 23:28 ` Rick Jones
2009-11-09 17:23 ` Caitlin Bestler
2009-11-09 17:36 ` Patrick McHardy
2009-11-08 4:27 ` David Miller
2009-11-09 5:49 ` Peter P Waskiewicz Jr
2009-11-09 6:38 ` David Miller
2009-11-09 6:54 ` Peter P Waskiewicz Jr [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=1257749659.2609.6.camel@ppwaskie-mobl2 \
--to=peter.p.waskiewicz.jr@intel.com \
--cc=davem@davemloft.net \
--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