On (06/16/09 20:34), Peter Memishian wrote: > > > > > en_10gfdx_cap=1,en_10ghdx_cap=..,en_1000fdx_cap=..,en_1000hdx_cap=..,en_100fdx_cap=..,en_100hdx_cap=.., > en_10fdx_cap=..,en_10hdx_cap=.. > > Which case? Certainly not in the model I'm suggesting, as those > properties no longer would exist.
As I understand it, the datalink.conf would have some line like en_mii=10g-f,1000M-fh,100M-.., 10M-.. (even if only one of these were modified from the default). And it has to be done this way because there's no concept of removing something from the en-mii set- only listing current members in the set. And if my understanding is right, then each restart of the drvier is going to go and do a (potentially redundant) set-linkprop of each value in the en_mii line above. And if someone updates the defaults driver source code, they now have to deal with what happens to existing datalink.conf entries. > > I don't know why you think this is being proposed. If someone tunes > en-mii, then there will be a recorded value for it that will be set when > the link is created. If there is not a setting for en-mii, then no value > will be set when the link is created. How do you record removal of an element from the set in your model, without enumerating all of (the current snapshot) of the set? What I'm proposing (using the "no-<sp>-<duplex>") would record just the removal of the element. Other driver defaults will remain untouched, for the driver to initialize. --Sowmini
