Subject: Re: meant hlist_* - Re: hash_list and rcu locking question

From: "Paul E. McKenney" <[email-masked]>
Date: Fri, 8 Aug 2008 15:21:17 -0700

On Thu, Aug 07, 2008 at 03:49:43AM +0200, Tobias Koeck wrote:
> I mean the rcu function for the hlist_{head,list} ....

There are some examples in http://lwn.net/Articles/262464/

This document notes that updates must be protected by some sort of
synchronization mechanism, for example, a lock.  RCU protects the
readers.

Additional information is available at http://lwn.net/Articles/263130/
and http://lwn.net/Articles/264090/

							Thanx, Paul

> Greetings
> t.
> 
> On Wed, Aug 6, 2008 at 10:54 PM, Evgeniy Polyakov <[email-masked]> wrote:
> > Hi Tobias.
> >
> > On Wed, Aug 06, 2008 at 05:56:43PM +0200, Tobias Koeck ([email-masked]) wrote:
> >> Are the hash_list rcu functions avoiding all locking problems (even
> >> the one with only one CPU)?
> >
> > What is hash list? hlist? Or list in a hash bucket?
> > Does include/linux/rculist.h contain needed bits?
> >
> >> Are there some abstract examples for the use of the hash_{head,list} structures?
> >
> > Sorry, my kernel source tree does not know what is 'hash_head'.
> > What data structure exactly do you mean?
> >
> > --
> >        Evgeniy Polyakov
> >
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to [email-masked]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html