On Tue, 2005-15-11 at 08:02 -0500, jamal wrote:

> I didnt see this issue as any different than setting any other current
> netdevice flags which goes via dev_change_flags; i gave the example of
> IFF_UP in my email because it sets the dev->state (invoked via
> dev->open/close). In the case of user space 802.1x - i assume the user
> space code is going to drive the state transitions by changing the
> netdevice->flags, no?
> 

Let me expand some more  (since i am gonna disappear again for a 10-12
hours):

I believe, after some coffee, all oper state should be read only from
user space. The control of the oper state will need to go via admin
state (like IFF_UP) - after all that is what "admin" means.

Having said that, perhaps thats where the concept of useroverride you
have or IFF_WAIT needs to go. What should be done though is to select an
"operational" mode via admin flags - example "the device is set by the
admin to dormant state" or "the device is set to dial-on-demand mode"
etc. 


cheers,
jamal





-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to