From: Rick Jones <rick.jones2@hp.com>
To: Bill Fink <billfink@mindspring.com>
Cc: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Caitlin Bestler <caitlin.bestler@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: RFC: ethtool support for n-tuple filter programming
Date: Sat, 07 Nov 2009 15:28:31 -0800 [thread overview]
Message-ID: <4AF6029F.6020403@hp.com> (raw)
In-Reply-To: <20091107144938.82957125.billfink@mindspring.com>
Bill Fink wrote:
> On Fri, 06 Nov 2009, Peter P Waskiewicz Jr wrote:
>
>
>>On Fri, 2009-11-06 at 11:12 -0800, Caitlin Bestler wrote:
>>
>>>The approach you are proposing assumes what type of packet filters
>>>that L2 hardware could support.
>>>
>>>Why not simply use existing filtering rules that overshoot the target,
>>>such as netfilter, and ask the
>>>device specific tool to indicate what set of these rules it can support?
>>
>>Are you proposing that netfilter is modified to pass the filters down to
>>the hardware if it supports it? netfilter doesn't steer flows though to
>>queues (or flow ID's in the kernel), plus that's putting HW-specific
>>capabilities into netfilter. I'm not sure we want to do that.
>>
>>Please correct me if I'm wrong with interpreting your suggestion.
>
>
> Plus I believe using netfilter has a significant performance penalty,
> and it would be desirable to use such a feature without incurring
> this penalty when there was otherwise no need to use netfilter.
At the risk of typing words into someone's keyboard, I interpreted it as
suggesting using the filtering language of netfilter or something similar, not
necessarily netfilter itself?
rick jones
next prev parent reply other threads:[~2009-11-07 23:28 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 [this message]
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
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=4AF6029F.6020403@hp.com \
--to=rick.jones2@hp.com \
--cc=billfink@mindspring.com \
--cc=caitlin.bestler@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@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).