[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: Glen Turner <glen.turner@xxxxxxxxxxxxx>
Date: Sun, 08 Aug 2004 14:08:36 +0930
Cc: Stephen Hemminger <shemminger@xxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <20040807211036.GA7970@xxxxxxxxxxxxxxx>
Organization: Australian Academic and Research Network
References: <20040806091305.4d405664@xxxxxxxxxxxxxxxxxxxxx> <20040806132145.675fd17d.davem@xxxxxxxxxx> <20040806143928.711d92eb@xxxxxxxxxxxxxxxxxxxxx> <20040807211036.GA7970@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707
bert hubert 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.

Hi Bert,

Please don't be so absolute. For example, if the virtual device "link" status
doesn't reflect that of the real device then routing software needs to parse
the virtual->real device mappings (a parsing for which Linux provides only
limited support).

Worse still, we now need to special-case virtual interfaces in application
   while (virtual_interface(interface_name)) {
     virtual_to_real(interface_name, &interface_name);

This is the sort of nasty detail than operating systems are meant to abstract
away from application code.


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