On Thu, 14 Dec 2006 00:31:28 +0100
Adrian Bunk <[email protected]> wrote:
> On Thu, Dec 14, 2006 at 12:18:48AM +0100, Thomas Graf wrote:
> > * Adrian Bunk <[email protected]> 2006-12-14 00:12
> > > On Wed, Dec 13, 2006 at 03:01:43PM -0800, Stephen Hemminger wrote:
> > > > Loopback should be there before protocols are started. It makes sense
> > > > to have a standard startup order.
> > >
> > > This actually becomes easier after my patch:
> > >
> > > Now that it's untangled from net_olddevs_init(), you can simply change
> > > the module_init(loopback_init) to a different initcall level.
> >
> > Not really, the device management inits as subsys, the ip layer hooks
> > into fs_initcall() which comes right after. The loopback was actually
> > registered after the protocol so far. I think Adrian's patch is fine
> > if the module_init() is changed to device_initcall().
>
> It doesn't matter (and I don't care) since for the non-modular case
> (that always applies for loopback), there's:
> #define __initcall(fn) device_initcall(fn)
> #define module_init(x) __initcall(x);
>
> cu
> Adrian
>
But what if other network device is not a module. We want loopback
to be first. so it needs to be before other device_initcall's
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
