From: Dipankar Sarma <dipankar@in.ibm.com>
To: BALBIR SINGH <balbir.singh@wipro.com>
Cc: "Paul E. McKenney" <pmckenne@us.ibm.com>,
lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: RFC: patch to allow lock-free traversal of lists with insertion
Date: Tue, 9 Oct 2001 14:18:32 +0530 [thread overview]
Message-ID: <20011009141832.B10410@in.ibm.com> (raw)
In-Reply-To: <200110090155.f991tPt22329@eng4.beaverton.ibm.com> <3BC2A3B3.3020004@wipro.com> <20011009131626.A10410@in.ibm.com> <3BC2B399.8030000@wipro.com>
In-Reply-To: <3BC2B399.8030000@wipro.com>; from balbir.singh@wipro.com on Tue, Oct 09, 2001 at 01:51:45PM +0530
On Tue, Oct 09, 2001 at 01:51:45PM +0530, BALBIR SINGH wrote:
> Dipankar Sarma wrote:
>
> >Either you see the element or you don't. If you want to avoid duplication,
> >you could do a locked search before inserting it.
> >Like I said before, lock-less lookups are useful for read-mostly
> >data. Yes, updates are costly, but if they happen rarely, you still benefit.
> >
> How does this compare to the Read-Copy-Update mechanism? Is this just another way of implementing
> it, given different usage rules.
Fundamentally, yes, RCU is a method for lock-less lookup. It is just
that RCU is elaborate enough to allow you deletion and freeing of
data as well.
Thanks
Dipankar
--
Dipankar Sarma <dipankar@in.ibm.com> Project: http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2001-10-09 8:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 1:55 RFC: patch to allow lock-free traversal of lists with insertion Paul E. McKenney
2001-10-09 2:18 ` David S. Miller
2001-10-09 6:52 ` Richard Henderson
2001-10-09 9:03 ` Rusty Russell
2001-10-09 16:11 ` Richard Henderson
2001-10-10 1:39 ` Rusty Russell
2001-10-09 7:13 ` BALBIR SINGH
2001-10-09 7:46 ` Dipankar Sarma
2001-10-09 8:21 ` BALBIR SINGH
2001-10-09 8:48 ` Dipankar Sarma [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 5:27 Paul McKenney
2001-10-09 5:56 ` David S. Miller
2001-10-09 6:43 ` Richard Henderson
2001-10-09 15:24 Paul McKenney
2001-10-09 15:28 Paul McKenney
2001-10-09 15:45 Paul McKenney
2001-10-09 17:00 ` Richard Henderson
2001-10-10 3:33 ` Paul Mackerras
2001-10-10 17:02 ` Richard Henderson
2001-10-09 16:51 Manfred Spraul
2001-10-09 17:46 Paul McKenney
2001-10-09 18:01 Paul McKenney
2001-10-10 1:19 Paul McKenney
2001-10-10 1:43 ` Andrea Arcangeli
2001-10-10 21:47 Paul McKenney
2001-10-10 22:22 ` Richard Henderson
2001-10-10 22:27 ` Richard Henderson
2001-10-11 1:56 Paul E. McKenney
2001-10-12 4:14 ` Rusty Russell
2001-10-13 14:48 ` 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=20011009141832.B10410@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=balbir.singh@wipro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=pmckenne@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