[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090428.064340.193569214.davem@davemloft.net>
Date: Tue, 28 Apr 2009 06:43:40 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mingo@...e.hu
Cc: dada1@...mosbay.com, torvalds@...ux-foundation.org,
shemminger@...tta.com, zbr@...emap.net, peterz@...radead.org,
mathieu.desnoyers@...ymtl.ca, jarkao2@...il.com, paulus@...ba.org,
paulmck@...ux.vnet.ibm.com, kaber@...sh.net,
jeff.chua.linux@...il.com, laijs@...fujitsu.com,
jengelh@...ozas.de, r000n@...0n.net, linux-kernel@...r.kernel.org,
netfilter-devel@...r.kernel.org, netdev@...r.kernel.org,
benh@...nel.crashing.org
Subject: Re: [PATCH] netfilter: use per-CPU r**ursive lock {XV}
From: Ingo Molnar <mingo@...e.hu>
Date: Tue, 28 Apr 2009 14:40:33 +0200
> IMHO this locking construct should be considered for
> linux/local_lock.h and kernel/local_lock.c. Even if the netfilter
> code drops its use soon afterwards ;-)
If you can show me have to pass a per-cpu variable (the variable,
not a dereference of it) as an argument to an inline function,
I'll implement this :-)
It has to be dereferenced after local_bh_disable() for the
read side acquisition.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists