Re: [PATCH RFC 2/3] rcu: More rcu-variants for list manipulation
From: Jan Schönherr
Date: Sat Jul 23 2011 - 14:41:59 EST
Am 22.07.2011 18:21, schrieb Paul E. McKenney:
Please see below for some comments on issues you are probably already
well aware of -- just commenting, the code itself looks OK.
Nice to hear.
patch is in good shape, it should probably go with the following patch
(which uses it) rather than up -rcu.
Okay. Whether I'll put this code into good shape or not depends
a bit on the last patch using this functionality.
You are of course right with the missing comments, but if this way of solving
the problem is rejected (or has some other problems that I might have
overlooked), then there is no point in writing all the comments...
(That is also why I did not put you on CC yet.)
If we decide to do it that way, you will get an updated version, hopefully
with all the comments you want to see in there. :)
+static inline void __list_link_rcu(struct list_head *prev,
+ struct list_head *next)
+ rcu_assign_pointer(list_next_rcu(prev), next);
+ next->prev = prev;
OK, so this one links a single list element to another single list
element. You therefore need two calls to this to splice a pair of list
Yes (or to the non-rcu version).
If so, there will be a time when you have a "6" shaped
list, so that readers from one of the list heads will never come back
to that list head. This is probably what you are getting at with your
"require that there are either no concurrent readers on the list to be
spliced or that these readers are still from the list where the list is
Exactly. No reader must get trapped in a circle. They all must be able
to return to their list head.
However, this is quite subtle and needs to be spelled out carefully.
I will try to do that.
Really badly need a header comment here!!! Which of these lists can
tolerate concurrent readers? Why are there three arguments? My guess
from the code is that "list" is the list being spliced, and it cannot
tolerate concurrent readers, while "prev" is one end of the place to
splice into the list and "next" is the other. I believe that both "prev"
and "next" can tolerate concurrent readers.
Did I get it right?
Regarding the function arguments, I tried to mimic those of the non-rcu
+static inline void __list_splice_rcu(struct list_head *list,
+ struct list_head *prev,
+ struct list_head *next)
+ __list_link(list->prev, next);
At this point, RCU readers traversing the list containing "prev" and
"next" see no change, which is why it is OK to use __list_link() rather
than __list_link_rcu(). If there are readers traversing "list", they
will loop infinitely failing to find the old list header.
Either that, or they do something worse as they mistake the new list
header for a normal node and try to access some of the elements of the
surrounding struct, which does not exist in this case.
+ __list_link_rcu(prev, list->next);
At this point, new RCU readers traversing the list containing
"next" and "prev" suddenly see the new elements from "list". The
rcu_assign_pointer() in __lists_link_rcu() should force proper ordering.
OK, so looks reasonable. Assuming that my guesses about what this is
supposed to do are correct, anyway.
I should probably say something about possible the use cases of this:
One could of course rewrite the already existing rcu-splice function to use
this low level funtionality.
But it gets more interesting if you want to add multiple elements to an
rcu-protected list: Instead of doing that one by one with list_add_rcu()
you can assemble them in a non-rcu list and splice them (avoiding quite
a few memory barriers).
The use case in the 3rd patch is even more special: The elements that
are spliced were removed from the very same list previously and there
might still be readers on them from before the removal. Due to this we
cannot collect this batch in a new list. But we can link one deleted
entry to the next (using the non-rcu(!) __list_link) building up a chain
of deleted entries. If there was a reader, it will find its way back
to the list over the last element in that chain. That chain is then
passed to the splice function.
(That chain-handling is currently in the third patch. I wonder whether
we should move that to one of the header files, too?!)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/