[Top] [All Lists]

Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!

To: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Subject: Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!)
From: Chris Wedgwood <cw@xxxxxxxx>
Date: Sun, 7 Jan 2001 16:29:05 +1300
Cc: linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>
In-reply-to: <3A578F27.D2A9DF52@xxxxxxxxxxxxxxx>; from greearb@xxxxxxxxxxxxxxx on Sat, Jan 06, 2001 at 02:33:27PM -0700
References: <3A578F27.D2A9DF52@xxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Sat, Jan 06, 2001 at 02:33:27PM -0700, Ben Greear wrote:

    I'm hoping that I can get a few comments on this code.  It was
    added to (significantly) speed up things like 'ifconfig -a' when
    running with 4000 or so VLAN devices.  It should also help other
    instances with lots of (virtual) devices, like FrameRelay, ATM,
    and possibly virtual IP interfaces.  It probably won't help
    'normal' users much, and in it's final form, should probably be a
    selectable option in the config process.

Virtual IP interfaces in the form of ifname:<number> (e.g. eth:1) IMO
should be deprecated and removed completely in 2.5.x. It's an ugly
external wart that should be removed.

That said, if this was done -- how would things like routing daemons
and bind cope? Actually, when I think about it they can't cope with
situating like this now:

tapu:~# ip addr show lo
1: lo: <LOOPBACK,UP> mtu 3904 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet scope host lo
    inet scope global lo


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