"Daniel L. Rall" wrote:
>
> Hello list. :)
>
> I rewrote the dev_alloc_name() function in the 2.2.14 Linux kernel's
> net/core/dev.c module. It had an apparently artificial limitation on
> number of network devices of the same type allowed (100), and was not
> implemented in a very efficient manner (which would not be a big deal
> under normal circumstances, as this routine wouldn't be called very
> often). Just another drop in the bucket. :)
I needed more for my VLAN implementation, and just upped the
100 to 8096 or so. Due to people's varying tastes, I also implemented
a few other methods of generating VLAN device names, and did NOT
even use the dev_alloc_name method in these instances.
So:
1) Will that screw your patch up? (I don't think it will...)
2) I'm curious what instances of device naming this patch could help.
For example, if you are going to have 200 devices of some type, then
you may not want them linearly named because as soon as you blink you
have forgotten what foo_dev198 refered to. At least from the comments
I've read relating to VLANs, it seems that a more direct naming scheme:
[base_dev]:[new_dev_id], ie: eth0:25 for a VLAN 25 on eth0, or something
similar, may be more desirable.
Thanks,
Ben
--
Ben Greear (greearb@xxxxxxxxxxxxxxx) http://www.candelatech.com
Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL)
http://scry.wanfear.com http://scry.wanfear.com/~greear
|