From: eran@nbase.co.il (Eran Man)
To: vlan@Scry.WANfear.com
Cc: "David S. Miller" <davem@redhat.com>,
Dax Kelson <dkelson@gurulabs.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Holger Kiehl <Holger.Kiehl@dwd.de>,
"vlan-devel (other)" <vlan-devel@lists.sourceforge.net>,
Lennert <buytenh@gnu.org>, Gleb Natapov <gleb@nbase.co.il>
Subject: Re: [VLAN] Re: Should VLANs be devices or something else?
Date: Wed, 20 Jun 2001 10:10:47 +0200 [thread overview]
Message-ID: <3B305A87.E4CAD52@nbase.co.il> (raw)
In-Reply-To: <3B2FCE0C.67715139@candelatech.com> <Pine.LNX.4.33.0106191641150.17061-100000@duely.gurulabs.com> <15151.55017.371775.585016@pizda.ninka.net> <3B2FDD62.EFC6AEB1@candelatech.com>
Ben Greear wrote:
>
> "David S. Miller" wrote:
> > Conceptually, svr4 streams are a beautiful and elegant
> > mechanism. :-)
> >
> > Technical implementation level concerns need to be considered
> > as well as "does it look nice".
>
> I found it to be the easiest way to implement things. It allowed
> me to not have to touch any of layer 3, and I did not have to patch
> any user-space program like ip or ifconfig.
>
> I'm not even sure if the nay-sayers ever had another idea, they
> just didn't like having lots of interfaces. Originally, there
> were claims of inefficiency, but it seems that other than things
> like 'ip' and ifconfig, there are no serious performance problems
> I am aware of.
There is the issue with netlink notification of large number of events.
See the mail thread starting from:
http://oss.sgi.com/projects/netdev/mail/netdev/msg01879.html
next prev parent reply other threads:[~2001-06-20 7:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 8:19 VLAN in kernel? Holger Kiehl
2001-06-19 22:11 ` Should VLANs be devices or something else? Ben Greear
2001-06-19 22:45 ` Dax Kelson
2001-06-19 22:49 ` David S. Miller
2001-06-19 22:52 ` Dax Kelson
2001-06-19 23:16 ` Ben Greear
2001-06-20 0:31 ` Marcell Gal
2001-06-20 1:24 ` [VLAN] " Ben Greear
2001-06-20 8:10 ` Eran Man [this message]
2001-06-20 9:32 ` Gleb Natapov
2001-06-20 7:21 ` [VLAN] " Sander Steffann
2001-06-22 6:12 ` Peter C. Norton
2001-06-22 6:27 ` Albert D. Cahalan
2001-06-22 6:36 ` Ben Greear
2001-06-21 22:10 ` [Vlan-devel] " Guy Van Den Bergh
2001-06-21 22:54 ` Ben Greear
2001-06-22 15:00 ` Matthias Welwarsky
2001-06-22 15:46 ` Chris Wedgwood
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=3B305A87.E4CAD52@nbase.co.il \
--to=eran@nbase.co.il \
--cc=Holger.Kiehl@dwd.de \
--cc=buytenh@gnu.org \
--cc=davem@redhat.com \
--cc=dkelson@gurulabs.com \
--cc=gleb@nbase.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=vlan-devel@lists.sourceforge.net \
--cc=vlan@Scry.WANfear.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.