> A very good reason why you would want them to have separate ifindices.
> Essentially, vlans have to be separate interfaces today. Other "virtual"
> interfaces such as aliased devices are not going to work with route
> daemons today since they dont meet this requirement.
>
> Not to rain on Ben's parade but:
> My thought was to have the vlan be attached on the interface ifa list and
> just give it a different label since it is a "virtual interface" on top
> of the "physical interface". Now that you mention the SNMP requirement,
> maybe an idea of major:minor ifindex makes sense. Say make the ifindex
> a u32 with major 16 bit and minor 16 bit. This way we can have upto 2^16
> physical interfaces and upto 2^16 virtual interfaces on the physical
> interface. The search will be broken into two 16 bits.
What problem does this fix?
If you are mucking with the ifindex, you may be affecting many places
in the rest of the kernel, as well as user-space programs which use
ifindex to bind to raw devices.
On the other hand, the hash patch touches only one file, and should
not have any external impacts.
>
> Thoughts?
>
> cheers,
> jamal
-- Ben Greear (greearb@candelatech.com) http://www.candelatech.com Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL) http://scry.wanfear.com http://scry.wanfear.com/~greear - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/