From: Rick Jones <rick.jones2@hp.com>
To: Linux Network Development list <netdev@vger.kernel.org>
Subject: Question about David's blog entry for NetCONF 2006, Day 1
Date: Thu, 21 Sep 2006 15:15:14 -0700 [thread overview]
Message-ID: <45130EF2.2090509@hp.com> (raw)
I was reading David's blog entries on the netdev meeting in Japan, and
have a question about this bit:
> Currently, things like Xen have to put the card into promiscuous
> mode, accepting all packets, which is quite inefficient.
Is the inefficient bit meant for accepting all packets, or more broadly
that the promiscuous path is quite inefficient compared to the
non-promiscuous path?
I ask because I would have thought that if the system were connected to
a switch (*), the number of packets received through a NIC in
promiscuous mode would be nearly the same as when it was not in
promiscuous mode - the delta being (perhaps) multicast frames.
rick jones
(*) "Today," it seems 99 times out of 10 systems are connected to
switches not hubs.
next reply other threads:[~2006-09-21 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 22:15 Rick Jones [this message]
2006-09-22 15:47 ` Question about David's blog entry for NetCONF 2006, Day 1 Brent Cook
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=45130EF2.2090509@hp.com \
--to=rick.jones2@hp.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).