From: Pavel Machek <pavel@suse.cz>
To: Dipankar Sarma <dipankar@in.ibm.com>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>,
linux-kernel@vger.kernel.org,
Paul McKenney <paul.mckenney@us.ibm.com>
Subject: Re: [PATCH] Read-Copy Update 2.5.4-pre2
Date: Sun, 10 Feb 2002 00:19:25 +0100 [thread overview]
Message-ID: <20020209231925.GA116@elf.ucw.cz> (raw)
In-Reply-To: <20020208234217.A18466@in.ibm.com> <Pine.LNX.4.33.0202081847020.30304-100000@coffee.psychology.mcmaster.ca> <20020209114818.C19737@in.ibm.com>
In-Reply-To: <20020209114818.C19737@in.ibm.com>
Hi!
> > > in lkml in the past. Currently there are several potential
> > > applications of RCU that are being developed and some of them look
> > > very promising. Our revamped webpage
> >
> > yes, but have you evaluated whether it's noticably better than
> > other forms of locking? for instance, couldn't your dcache example
> > simply use BR locks?
>
> First of all, IMO, RCU is not a wholesale replacement for one form of
> locking or another. It provides two things -
>
> 1. Simplify locking in certain complicated cases - like module
> unloading or Hotplug CPU support.
I thought that refrigerator mechanism might be handy for hotplug CPU
support -- essentially stop whole userland, do your job, restart
userland... Its part of swsusp.
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
prev parent reply other threads:[~2002-02-10 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 18:12 [PATCH] Read-Copy Update 2.5.4-pre2 Dipankar Sarma
2002-02-08 23:51 ` Mark Hahn
2002-02-08 23:54 ` Robert Love
2002-02-09 6:56 ` Dipankar Sarma
2002-02-09 8:30 ` Andrea Arcangeli
2002-02-09 6:18 ` Dipankar Sarma
2002-02-09 23:19 ` Pavel Machek [this message]
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=20020209231925.GA116@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=dipankar@in.ibm.com \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@us.ibm.com \
/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