Re: Kernel rwlock design, Multicore and IGMP

From: Eric Dumazet
Date: Mon Nov 15 2010 - 06:31:22 EST

Next message: Andi Kleen: "Re: [PATCH 1/2] perf-events: Add support for supplementary eventregisters v2"
Previous message: Christoph Hellwig: "Re: [PATCH] jbd2: avoid the concurrent data writeback"
In reply to: Cypher Wu: "Re: Kernel rwlock design, Multicore and IGMP"
Next in thread: Chris Metcalf: "[PATCH] arch/tile: fix rwlock so would-be write lockers don't block new readers"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Le lundi 15 novembre 2010 Ã 19:18 +0800, Cypher Wu a Ãcrit :
> In that post I want to confirm another thing: if we join/leave on
> different cores that every call will start the timer for IGMP message
> using the same in_dev->mc_list, could that be optimized?
>

Which timer exactly ? Is it a real scalability problem ?

I believe RTNL would be the blocking point actually...

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Andi Kleen: "Re: [PATCH 1/2] perf-events: Add support for supplementary eventregisters v2"
Previous message: Christoph Hellwig: "Re: [PATCH] jbd2: avoid the concurrent data writeback"
In reply to: Cypher Wu: "Re: Kernel rwlock design, Multicore and IGMP"
Next in thread: Chris Metcalf: "[PATCH] arch/tile: fix rwlock so would-be write lockers don't block new readers"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]