From: Glen Turner <glen.turner@aarnet.edu.au>
To: bert hubert <ahu@ds9a.nl>
Cc: Stephen Hemminger <shemminger@osdl.org>,
"David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com
Subject: Re: [PATCH 2.6] vlan ioctl propagation (rev.2)
Date: Sun, 08 Aug 2004 14:08:36 +0930 [thread overview]
Message-ID: <4115AE4C.2060608@aarnet.edu.au> (raw)
In-Reply-To: <20040807211036.GA7970@outpost.ds9a.nl>
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
code:
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.
Thanks,
Glen
next prev parent reply other threads:[~2004-08-08 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040806091305.4d405664@dell_ss3.pdx.osdl.net>
[not found] ` <20040806132145.675fd17d.davem@redhat.com>
2004-08-06 21:39 ` [PATCH 2.6] vlan ioctl propagation (rev.2) Stephen Hemminger
2004-08-07 21:10 ` bert hubert
2004-08-08 4:38 ` Glen Turner [this message]
2004-08-08 10:14 ` bert hubert
2004-08-09 15:53 ` Stephen Hemminger
2004-08-09 23:45 ` David S. Miller
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=4115AE4C.2060608@aarnet.edu.au \
--to=glen.turner@aarnet.edu.au \
--cc=ahu@ds9a.nl \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).