[lkml]   [2006]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch] ipv4: initialize arp_tbl rw lock
    > > Ok, so the problem seems to be that inet_init gets called after qeth_init.
    > > Looking at the top level Makefile this seems to be true for all network
    > > drivers in drivers/net/ and drivers/s390/net/ since we have
    > >
    > > vmlinux-main := $(core-y) $(libs-y) $(drivers-y) $(net-y)
    > >
    > > The patch below works for me... I guess there must be a better way to make
    > > sure that any networking driver's initcall is made before inet_init?
    > >
    > > Signed-off-by: Heiko Carstens <>
    > We could make inet_init() a subsystem init but I vaguely recall
    > that we were doing that at one point and it broke things for
    > some reason.
    > Perhaps fs_initcall() would work better. Or if that causes
    > problems we could create a net_initcall() that sits between
    > fs_initcall() and device_initcall().
    > Or any other ideas?

    Tried to figure out what is causing the delays I experienced when I replaced
    module_init() in af_inet.c with fs_initcall(). After all it turned out that
    synchronize_net() which is basicically nothing else than synchronize_rcu()
    sometimes takes several seconds to complete?! No idea why that is...

    callchain: inet_init() -> inet_register_protosw() -> synchronize_net()
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-04-15 09:30    [W:0.021 / U:23.728 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site