From: Jeff Garzik <jgarzik@pobox.com>
To: jamal <hadi@cyberus.ca>
Cc: Donald Becker <becker@scyld.com>,
Ben Greear <greearb@candelatech.com>,
netdev@oss.sgi.com
Subject: Re: SIOCADDMULTI for unicast broken
Date: Sat, 04 Jan 2003 02:32:54 -0500 [thread overview]
Message-ID: <3E168E26.1030006@pobox.com> (raw)
In-Reply-To: <20030103224852.L48869@shell.cyberus.ca>
I wonder if there are any good uses for more advanced RX filtering that
is beginning to appear. I could certainly imagine an interface that was
a more generic RX filtering interface, and [just by accident] happened
to support existing unicast and multicast rx-mode-related controls.
As vendors stuff features onto cards and try to figure out where is the
best dividing line between TCP stack acceleration and TCP stack offload,
it seems to me that recent cards more often than not have nice RX
filtering capabilities. If you look at the world through GigE-colored
glasses, the RX filtering picture gets even better. There are some fun
SMP implications with flexible enough RX filtering, for example.
next prev parent reply other threads:[~2003-01-04 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 21:46 SIOCADDMULTI for unicast broken jamal
2003-01-04 0:07 ` Donald Becker
2003-01-04 1:18 ` Jeff Garzik
2003-01-04 1:39 ` Donald Becker
2003-01-04 1:45 ` Ben Greear
2003-01-04 1:52 ` Jeff Garzik
2003-01-06 15:00 ` Krzysztof Halasa
2003-01-04 2:18 ` Donald Becker
2003-01-04 4:11 ` jamal
2003-01-04 6:33 ` Donald Becker
2003-01-04 17:41 ` jamal
2003-01-04 18:24 ` Donald Becker
2003-01-04 18:55 ` jamal
2003-01-04 18:36 ` Julian Anastasov
2003-01-04 19:04 ` jamal
2003-01-05 11:45 ` Julian Anastasov
2003-01-06 13:44 ` jamal
2003-01-06 15:00 ` Julian Anastasov
2003-01-06 17:23 ` jamal
2003-01-04 7:32 ` Jeff Garzik [this message]
2003-01-04 17:43 ` jamal
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=3E168E26.1030006@pobox.com \
--to=jgarzik@pobox.com \
--cc=becker@scyld.com \
--cc=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.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).