From: Thomas Gleixner <tglx@linutronix.de>
To: Urs Thuermann <urs@isnogud.escape.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: locking mechanisms
Date: Sat, 01 Jul 2006 11:36:11 +0200 [thread overview]
Message-ID: <1151746571.25491.850.camel@localhost.localdomain> (raw)
In-Reply-To: <m2odw9g937.fsf@janus.isnogud.escape.de>
Urs,
On Sat, 2006-07-01 at 07:58 +0200, Urs Thuermann wrote:
> So my question is, is it really necessary for the list traversal to be
> atomic, i.e. to disable preemption? According to "Linux Device
> Drivers", this is needed for the callback function, so it can be
> called after the scheduler has been run on all CPUs and no reader is
> still accessing the list item to be freed. Is it right, that the
> rcu_read_lock() wouldn't be necessary if I only would call
> list_add_rcu() and list_del_rcu() since these make atomic changes and
> can run in parallel anyway, even with rcu_read_lock(), on a SMP
> system?
Does Documentation/listRCU.txt answer your questions ?
tglx
next prev parent reply other threads:[~2006-07-01 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 5:58 Q: locking mechanisms Urs Thuermann
2006-07-01 9:36 ` Thomas Gleixner [this message]
2006-07-02 5:26 ` Urs Thuermann
2006-07-04 12:58 ` Urs Thuermann
2006-07-05 6:11 ` Paul E. McKenney
2006-07-05 9:35 ` Urs Thuermann
2006-07-05 14:13 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1151746571.25491.850.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=urs@isnogud.escape.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox