[Top] [All Lists]

Re: [PATCH 2.6] vlan ioctl propagation (rev.2)

To: bert hubert <ahu@xxxxxxx>
Subject: Re: [PATCH 2.6] vlan ioctl propagation (rev.2)
From: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Mon, 9 Aug 2004 08:53:48 -0700
Cc: "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <20040807211036.GA7970@xxxxxxxxxxxxxxx>
Organization: Open Source Development Lab
References: <20040806091305.4d405664@xxxxxxxxxxxxxxxxxxxxx> <20040806132145.675fd17d.davem@xxxxxxxxxx> <20040806143928.711d92eb@xxxxxxxxxxxxxxxxxxxxx> <20040807211036.GA7970@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Sat, 7 Aug 2004 23:10:37 +0200
bert hubert <ahu@xxxxxxx> wrote:

> On Fri, Aug 06, 2004 at 02:39:28PM -0700, Stephen Hemminger wrote:
> > Here is a redo of the patch to propagate ethtool and mii ioctl's
> > on vlan's to the underlying real device.  This time the request
> > is copied to a new buffer, to avoid the colon name rewrite issues.
> Is this really what we want? We also don't make virtual IPs appear as real
> interfaces anymore. Virtual devices are just that - virtual.
> -- 
>      Open source, database driven DNS Software 
>           Linux Advanced Routing & Traffic Control HOWTO

The problem is that the bridge code (and bonding) want to be able to send 
ioctl's to the device.  The bridge wants it to find out the speed of the device
to set the spanning tree values appropriately. 
I would rather not special case VLAN's.

<Prev in Thread] Current Thread [Next in Thread>