[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090428.045342.206106171.davem@davemloft.net>
Date: Tue, 28 Apr 2009 04:53:42 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: dada1@...mosbay.com
Cc: torvalds@...ux-foundation.org, shemminger@...tta.com,
zbr@...emap.net, mingo@...e.hu, 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: Eric Dumazet <dada1@...mosbay.com>
Date: Tue, 28 Apr 2009 08:58:05 +0200
> I am not sure my day job will permit me to polish a patch mixing all
> the bits and comments. But I am glad we eventually got back spinlocks
> which are probably better than rwlocks for implementing this stuff.
>
> Instead of submitting a full patch again, we could first submit a new
> include file containg all comments and inline functions ?
>
> This include file could be local to netfilter, with a big stick on
> it to forbids its use on other areas (No changes in Documentation/ )
>
> Then, as soon as we can go back to pure RCU solution, we can safely
> delete this controversial-locking-nesting-per-cpu-thing ?
I say we merge Linus's locking idea into the XV patch, fixup the
commit message wording, and move on with life.
For something that's going to get deleted as soon as the faster grace
period RCU stuff is available, it has consumed an inordinate amount of
our time :-)
I might take a stab at this before hittng bed tonight, no promises :)
--
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