On 03/10/09 19:40, Peter Memishian wrote: > > > 3. provide per-interface prop support in ipadm and leave the "global" > > > setting alone (In addition to complicating our kernel tremendously, > > > I don't even see how this would work. E.g. if the "prop" > > > is some thing like a rate-limit parameter, and the value is different > > > for each interface, then what would the global value be?) > > [...] > > > None of these options is ideal, but #2 seems to make the best of > > > a bad-deal. Thoughts? > > > > I suggest a fifth possibility with two variants: > > > > 5. Leave the global variable alone. It becomes the 'default' for > > newly-plumbed interfaces. Interfaces can be configured away from > > that value, but the global doesn't reflect those changes. > > I'm concerned about a model where the global variable continues to serve a > userful function that cannot be otherwise filled. That is, unless the > "wildcard" mode you spoke of in a subsequent email does in fact include > all future IP interfaces,
That's correct. Absence of interface name in 'ipadm' command means all the current interfaces and all the future interfaces. To apply certain per-interface tunable, on few/all current interfaces, the user could always write a script to loop through all the desired interface and set that tunable one interface at a time. ~Girish
