In article <[EMAIL PROTECTED]> (at Thu, 2 Feb 2006 23:42:25 +1100), Herbert Xu <[EMAIL PROTECTED]> says:
> On Thu, Feb 02, 2006 at 05:37:22AM -0700, Eric W. Biederman wrote: > > > > > Yes you are right. The locking/refcounting in addrconf.c is such > > > a mess. I've asked a number of times before as to why most of > > > this can't be done in user-space instead. There is nothing performance > > > critical here, and the system must be able to deal with a device with > > > no IPv6 addresses anyway (think of the case when the device was up before > > > ipv6.ko was loaded). > > > > A lot of the latter case is handled by the replay of netdevice events > > when you register a netdevice notifier. > > Yes. What I meant is that it is normal to have a period of time during > which a device has no IPv6 addresses attached. Doing addrconf in the > kernel means that we can guarantee that as soon as a device appears we > slap on an IPv6 address. My point is that we need to cope with devices > without IPv6 addresses anyway. We SHALL do autoconf when we "up" an ipv6-capable device. It is the IPv6. I agree that, in SOME cases, some people want to disable ipv6 on some of their interfaces. --yoshfuji - 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
