On Thu, 2005-17-11 at 21:36 +0100, Stefan Rompf wrote:
> Am Donnerstag 17 November 2005 04:29 schrieb jamal:
>
> > > > 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".
>
> We can avoid a myriad of new IFF_*-flags if we allow a device driver to
> specify a function for mapping its internal state to RFC2863, like Thomas
> did. The result of that function will then be used as input for the link-oper
> mode policy.
>
I will wait for the patch to comment - I hope that from user space one
can find what the real oper state the netdevice is in.
> > I think IFF_RUNNING hasnt changed meaning in that it reflects the
> > operational DOWN/UP state. We may have to export two new IFF_XXX
> > operational flags to user space {IFF_DORMANT and IFF_LLD} like i was
> > suggesting earlier; i cant see any other way to escape exporting those
> > two if we are to maintain backward compat for IFF_RUNNING.
>
> It's debatable what backward compatibily for IFF_RUNNING means. From the view
> of a userspace application like zebra or dhcpcd, IFF_RUNNING should be set
> when the interface is actually usable - and that is after the 802.1X
> supplicant f.e. has finished and has raised operstate to OPER_UP.
>
IFF_RUNNING has always carried the meaning of oper up/down - I think we
are agreeing it should continue to hold that meaning; unless i
misunderstood you.
> > I hope the above is clear - any patch will have to be a mix of the ones
> > posted so far.
>
> ok, I'll produce a patch then - first version will be available tomorrow
> evening.
>
beauty.
> > If we are in agreement, i can post what i think the states are; although
> > if we are in agreement above i dont see the need to.
>
> I think I have a quite clear idea, but I don't want to keep you from
> posting ;-)
>
Unfortunately 2863 doesnt do a lot of justice and the states have to be
clearly interpreted.
I will attempt some ascii art shortly. Actually if you agree with it
please include it in your patch so it is easier for people to make
changes in the future.
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
