Hello!
> If those are in the critical path, then things like virtual web servers
> (say with 20 virtual ip interfaces on them), should see a noticable drop
> in performance, eh?
"Virtual IP interfaces" are split to separate level in 2.2.
They are _not_ _devices_ and you may create dozen of thousands
of them without harm.
See?
> finds it's way into these kinds of devices, someone will optimize it to
> better handle the large number of interfaces...
One day, when people understood that number of files sometimes becomes
pretty large, they invented "directories". Imagine, I worked on machines,
which had no "directories". I do not want to rememeber about
this experience. 8)8)
It does not mean, that device list must stay suboptimal.
But the things must be made in time. Plain list is enough for now,
and it dictates programming style.
> How else could you offer, say VLANs, without using interfaces?
Do you ask me? Think! 8)
> Layer 3 (IP & ARP) takes care of it for them. VLANs and PVCs are at lower
> layers,
> which are generally presented to the users as interfaces.
See above. When a level explodes, it must be split. No questions.
Invent a way to split it.
> Btw, I was planning on using source-routing (ie the ip command) in a
> PC with 20 real ethernet interfaces. Does this mean that the ip command
> will not support that?
8)8)8) ip was written specially to parse huge amounts of data.
But it helps to parse _well_ _structured_ data, rather than
flat data enumerated by random numbers.
Alexey
|