On Fri, 10 Mar 2006, Nick Piggin wrote:
> I'm writing some stuff about these patches, and I've uploaded a
> **draft** chapter on the RCU radix-tree, 'radix-intro.pdf' in above
> directory (note the bibliography didn't make it -- but thanks Paul
> McKenney!)
Ah thanks. I had a look at it. Note that the problem with the radix tree
tags is that these are inherited from the lower layer. How is the
consistency of these guaranteed? Also you may want to add a more elaborate
intro and conclusion. Typically these summarize other sections of the
paper.
What you are proposing is to allow lockless read operations right? No
lockless write? The concurrency issue that we currently have is multiple
processes faulting in pages in different ranges from the same file. I
think this is a rather typical usage scenario. Faulting in a page from a
file for reading requires a write operation on the radix tree. The
approach with a lockless read path does not help us. This proposed scheme
would only help if pages are already faulted in and another process starts
using the same pages as an earlier process.
Would it not be better to handle the radix tree in the same way as a page
table? Have a lock at the lowest layer so that different sections of the
radix tree can be locked by different processes? That would enable
concurrent writes.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
