Am Mittwoch 16 November 2005 03:16 schrieb jamal: > I will not respond to the rest of your email - I wanna make sure we are > in sync first on the above. So let me summarize:
Ok, let's see if I understood you: > 1) There are read_only oper state IFF_XXX flags which are sent via > netlink to user space. These are set by the kernel (and not by user > space); they reflect the state of "link". managed only by the device driver or several layers of the device driver. > 2) There are read/write admin IFF_XXX flags which are used to select > the link-oper mode. I made some suggestions in the earlier email and > referenced the BSD man pages. By default the state transition is from > Down<->UP. A mode could be selected to set a device so it goes from > Down<->Dormant. The setting of link-oper mode tells the kernel how to map the flags from 1) to 3) > 3) There is a kernel dev->operstate_kernel which is accessible via > user space in the same manner IFF_UP flags are set etc. Depending on the selected policy in 2), this state is managed by userspace and/or kernel and shows the RFC2863 operstate of the device. Note: To accomplish our goal to tell dhcp/router daemons when a device is ready for "real" traffic, IFF_RUNNING has to be derived from here. > Lets get in sync with the above first. All in all, I think my understanding of your idea would work and looks good. But if I still didn't get it, it really would be best if you are next in posting a patch or pseudo code ;-) Stefan - 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
