netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Caitlin Bestler <caitlinb@broadcom.com>
Cc: Leonid Grossman <Leonid.Grossman@neterion.com>,
	"David S. Miller" <davem@davemloft.net>,
	shemminger@osdl.org, alex@neterion.com, netdev@vger.kernel.org
Subject: Re: VJ Channel API - driver level (PATCH)
Date: Wed, 3 May 2006 22:07:40 +0400	[thread overview]
Message-ID: <20060503180740.GA14506@2ka.mipt.ru> (raw)
In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F149E880@NT-SJCA-0751.brcm.ad.broadcom.com>

On Wed, May 03, 2006 at 08:56:23AM -0700, Caitlin Bestler (caitlinb@broadcom.com) wrote:
> > I'd expect high end NIC ASICs to implement rx steering based
> > upon some sort of hash (for load balancing), as well as
> > explicit "1:1" steering between a sw channel and a hw
> > channel. Both options for channel configuration are present
> > in the driver interface.
> > If netfilter assists can be done in hardware, I agree the
> > driver interface will need to add support for these -
> > otherwise, netfilter processing will stay above the driver.
> > 
> > 
> 
> Even if the hardware cannot fully implement netfilter rules
> there is still value in having an interface that documents 
> exactly how much filtering a given piece of hardware can do.
> There is no point in having the kernel repeat packet classifications
> that have already been done by the NIC.

Please do not suppose that vj channel must rely on underlaying hardware.
New interface MUST work better or at least not worse than existing skb
queueing for majority of users, and I doubt users with netfilter capable
hardware are there.
It is only some hint to the SW, not rules, that hardware can provide.
The best would be ipv4/ipv6 hashing, and I think it is enough.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2006-05-03 18:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 15:56 VJ Channel API - driver level (PATCH) Caitlin Bestler
2006-05-03 18:07 ` Evgeniy Polyakov [this message]
2006-05-03 18:45   ` YOSHIFUJI Hideaki / 吉藤英明
2006-05-03 20:35   ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2006-05-03 20:40 Caitlin Bestler
2006-05-04 22:49 ` Alex Aizman
2006-05-04 23:04   ` David S. Miller
2006-05-05  9:36     ` Evgeniy Polyakov
2006-05-06  0:35       ` David S. Miller
2006-05-06  8:42         ` Evgeniy Polyakov
2006-05-06  8:57           ` Evgeniy Polyakov
2006-05-03 18:12 Caitlin Bestler
2006-05-03 18:49 ` Stephen Hemminger
2006-05-03 17:52 Caitlin Bestler
2006-05-03 13:56 Leonid Grossman
2006-05-03 20:23 ` David S. Miller
2006-05-02 22:53 Alex Aizman
2006-05-02 23:00 ` Stephen Hemminger
2006-05-03  6:47   ` David S. Miller

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=20060503180740.GA14506@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=Leonid.Grossman@neterion.com \
    --cc=alex@neterion.com \
    --cc=caitlinb@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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).