From: "David S. Miller" <davem@redhat.com>
To: Dax Kelson <dkelson@gurulabs.com>
Cc: Ben Greear <greearb@candelatech.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Holger Kiehl <Holger.Kiehl@dwd.de>,
VLAN Mailing List <vlan@Scry.WANfear.com>,
"vlan-devel (other)" <vlan-devel@lists.sourceforge.net>,
Lennert <buytenh@gnu.org>, Gleb Natapov <gleb@nbase.co.il>
Subject: Re: Should VLANs be devices or something else?
Date: Tue, 19 Jun 2001 15:49:13 -0700 (PDT) [thread overview]
Message-ID: <15151.55017.371775.585016@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0106191641150.17061-100000@duely.gurulabs.com>
In-Reply-To: <3B2FCE0C.67715139@candelatech.com> <Pine.LNX.4.33.0106191641150.17061-100000@duely.gurulabs.com>
Dax Kelson writes:
> On Tue, 19 Jun 2001, Ben Greear wrote:
> > Should VLANs be devices or some other thing?
>
> I would vote that VLANs be devices.
>
> Conceptually, VLANs as network devices is a no brainer.
Conceptually, svr4 streams are a beautiful and elegant
mechanism. :-)
Technical implementation level concerns need to be considered
as well as "does it look nice".
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-06-19 22:49 UTC|newest]
Thread overview: 20+ 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 [this message]
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
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
[not found] <3B2FCE0C.67715139@candelatech.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0106191641150.17061-100000@duely.gurulabs.com.suse.lists.linux.kernel>
[not found] ` <15151.55017.371775.585016@pizda.ninka.net.suse.lists.linux.kernel>
[not found] ` <3B2FDD62.EFC6AEB1@candelatech.com.suse.lists.linux.kernel>
2001-06-20 8:26 ` Andi Kleen
2001-06-20 14:59 ` Ben Greear
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=15151.55017.371775.585016@pizda.ninka.net \
--to=davem@redhat.com \
--cc=Holger.Kiehl@dwd.de \
--cc=buytenh@gnu.org \
--cc=dkelson@gurulabs.com \
--cc=gleb@nbase.co.il \
--cc=greearb@candelatech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®