[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491C4FA8.4020704@cosmosbay.com>
Date: Thu, 13 Nov 2008 17:02:48 +0100
From: Eric Dumazet <dada1@...mosbay.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
David Miller <davem@...emloft.net>
CC: Corey Minyard <minyard@....org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Stephen Hemminger <shemminger@...tta.com>,
benny+usenet@...rsen.dk,
Linux Netdev List <netdev@...r.kernel.org>,
Christoph Lameter <cl@...ux-foundation.org>,
Evgeniy Polyakov <zbr@...emap.net>,
Christian Bell <christian@...i.com>
Subject: [PATCH 4/3] rcu: documents rculist_nulls
Eric Dumazet a écrit :
> Peter Zijlstra a écrit :
>> So by not using some memory barriers (would be nice to have it
>> illustrated which ones), we can race and end up on the wrong chain, in
>> case that happens we detect this by using this per-chain terminator and
>> try again.
>>
>> It would be really good to have it explained in the rculist_nulls.h
>> comments what memory barriers are missing, what races they open, and how
>> the this special terminator trick closes that race.
>
> OK, maybe I should add a Documentation/RCU/rculist_nulls.txt file with
> appropriate examples and documentation.
>
> (Say the lookup/insert algorithms, with standard hlist and memory barriers,
> and with hlist_nulls without those two memory barriers.
>
[PATCH 4/3] rcu: documents rculist_nulls
Adds Documentation/RCU/rculist_nulls.txt file to describe how 'nulls'
end-of-list can help in some RCU algos.
Signed-off-by: Eric Dumazet <dada1@...mosbay.com>
---
Documentation/RCU/rculist_nulls.txt | 167 ++++++++++++++++++++++++++
1 files changed, 167 insertions(+)
View attachment "rculist_nulls_doc.patch" of type "text/plain" (5490 bytes)
Powered by blists - more mailing lists