[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <478FBEA0.9090203@gmail.com>
Date: Thu, 17 Jan 2008 21:46:24 +0100
From: Franck Bui-Huu <vagabon.xyz@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC: paulmck@...ux.vnet.ibm.com
Subject: [PATCH 0/2] Make RCU lists use the RCU API
Hi,
After reading the nice article contributed by Paul on LWN, I took a look
to the kernel RCU-protected list implementation to get a good idea on
how RCU protection mechanism can be used.
And it appears that the implementation doesn't use the RCU API as much
as it could: every updates of "->next" field could have been done by
using rcu_assign_pointer(), the main point being readability.
So this patchset does that. However when cooking the patch, I noticed
that it's hard to import RCU API without creating some circular
dependencies. This is mainly explained by the fact that list.h defines a
couple of very primitive types used all over the kernel.
The easiest thing I could come up with is to create a new header file
rculist.h, which keeps all RCU-protected list definitions. list.h still
keeps the basic list stuffs and still has very few dependencies. OTOH
RCU-protected list is a more complex type of list and can have more
dependencies. Therefore it needs more careful in including it.
I don't know if any header dependency rules exist for the kernel, so
please any suggestions are welcome to deal with such issue.
"make allyesconfig" builds and boots fine on x86 architecture, this
patchset being applied on top of Linus' v2.6.24-rc7 tag.
Please consider,
Franck
--
arch/ia64/sn/kernel/irq.c | 1 +
drivers/infiniband/hw/ipath/ipath_verbs_mcast.c | 3 +-
include/linux/dcache.h | 1 +
include/linux/list.h | 385 ----------------------
include/linux/rculist.h | 391 +++++++++++++++++++++++
lib/textsearch.c | 2 +-
6 files changed, 395 insertions(+), 388 deletions(-)
--
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