netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Jamal Hadi Salim <hadi@cyberus.ca>,
	Christophe Devriese <Christophe.Devriese@eurid.eu>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: Linville's L2 rant... -- Re: PATCH Fix bonding active-backup behavior for VLAN interfaces
Date: Tue, 1 Aug 2006 13:03:35 -0400	[thread overview]
Message-ID: <20060801170329.GG29208@tuxdriver.com> (raw)
In-Reply-To: <44CF7E8B.9030407@candelatech.com>

On Tue, Aug 01, 2006 at 09:17:15AM -0700, Ben Greear wrote:
> John W. Linville wrote:

> Well, if it makes you feel better, I can't see a good way to do
> vlans-over-vlans cleanly, backwards compatibly, and functional with
> bridging, etc.  I would not plan to add such a feature to the kernel
> unless from it's moment of inclusion it could handle at least bridging,
> either.  So that feature will probably not see the light of day
> any time soon :)

I suspected as much. :-)

> >Most (actually all afaik) L2 networking equipment enforces some
> >hierarchy on the relationship between these L2 entities.  I am more
> >and more convinced we should do the same, although I do acknowledge
> >that the current situation does allow for some cleverness.
> 
> Very often, the answer to difficult networking issues is to 'get a linux 
> box', since that very flexibility is often key to interesting problems.
 
No doubt that is true.  FWIW I think we would still have to be very
flexible about when/how/where vlan tagging gets done, if for no other
reason than that I can't seem to convince myself of any one place it
should go... :-)

Oh, and there may be no reason to ever remove the virtual device vlan
implementation, even if there was a nicer/cleaner/better L2 layer
for the other 90+%.

> >I'm just not sure that cleverness is worth the headache, especially
> >since the most clever things usually only work by accident...
> 
> Or, work by solid, modular design and small tweaks!

Point taken.  But stashing little hacks in the networking core for
specific virtual drivers isn't totally modular either.  And even if
it were, "modular design" probably belongs on the list of "things
that can be taken too far", like "everything in userland", "never
use ioctl", and "microkernels are superior". :-)

I definitely respect your contributions both past and (presumably)
future, and I have no doubt that you have seen any number of
'interesting' vlan scenarios.  Again, my complaint is more about
the overall lack of integration/coherence for L2 functions.  I have
few complaints about individual functions (that I wish to discuss in
this thread).

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2006-08-01 17:03 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28  9:44 PATCH Fix bonding active-backup behavior for VLAN interfaces Christophe Devriese
2006-07-28 16:01 ` Ben Greear
2006-07-28 21:50   ` Christophe Devriese
2006-07-28 21:55     ` Ben Greear
2006-07-28 22:15       ` Christophe Devriese
     [not found]       ` <20060728221455.GA25610@walrus.eth1.org>
     [not found]         ` <44CA8AF1.3020408@candelatech.com>
2006-07-28 22:58           ` Christophe Devriese
2006-07-28 22:55             ` David Miller
2006-07-28 23:14               ` Ben Greear
2006-07-31  3:50       ` David Miller
2006-07-31  8:15         ` Christophe Devriese
2006-07-31 12:30           ` Linville's L2 rant... -- " John W. Linville
2006-07-31 16:48             ` Christophe Devriese
2006-08-01  1:39             ` Jamal Hadi Salim
2006-08-01 12:08               ` John W. Linville
2006-08-01 12:33                 ` Jamal Hadi Salim
2006-08-01 16:10                   ` Ben Greear
2006-08-01 16:52                     ` John W. Linville
2006-08-01 17:04                       ` Ben Greear
2006-08-01 19:47                         ` Krzysztof Halasa
2006-08-01 16:48                   ` John W. Linville
2006-08-01 16:17                 ` Ben Greear
2006-08-01 17:03                   ` John W. Linville [this message]
2006-08-01 17:21                     ` Ben Greear
2006-08-02  9:02                       ` Christophe Devriese
2006-08-02 17:37                         ` Stackable devices Stephen Hemminger
2006-08-02 17:50                           ` Ben Greear
2006-08-08 12:03                             ` Christophe Devriese
2006-08-08 16:36                               ` Ben Greear
2006-08-09 13:57                                 ` Christophe Devriese
2006-08-12 18:43                                   ` Ben Greear
2006-08-12 19:29                                   ` Ben Greear
2006-08-02 20:58           ` PATCH Fix bonding active-backup behavior for VLAN interfaces David Miller
2006-08-03  9:18             ` Krzysztof Oledzki
2006-08-10 18:18               ` Krzysztof Oledzki
2006-08-11  6:45                 ` David Miller
2006-08-11  8:50                   ` Christophe Devriese
2006-08-11  8:53                     ` David Miller
2006-08-14  8:16                   ` Christophe Devriese
2006-08-14  8:47                     ` David Miller
2006-08-14  8:47                     ` David Miller
2006-08-03 13:34             ` Christophe Devriese
2006-08-04  1:01             ` Jay Vosburgh
2006-08-15  0:09               ` David Miller
2006-08-15 22:18                 ` Jay Vosburgh
2006-08-15 22:27                   ` David Miller
2006-08-16 19:30                 ` Krzysztof Oledzki
2006-08-20 19:41                 ` Christophe Devriese

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=20060801170329.GG29208@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Christophe.Devriese@eurid.eu \
    --cc=davem@davemloft.net \
    --cc=greearb@candelatech.com \
    --cc=hadi@cyberus.ca \
    --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).