From: Richard Henderson <rth@twiddle.net>
To: Paul McKenney <Paul.McKenney@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: RFC: patch to allow lock-free traversal of lists with insertion
Date: Tue, 9 Oct 2001 10:00:23 -0700 [thread overview]
Message-ID: <20011009100023.A27427@twiddle.net> (raw)
In-Reply-To: <OF296D0EDC.4D1AE07A-ON88256AE0.00568638@boulder.ibm.com>
In-Reply-To: <OF296D0EDC.4D1AE07A-ON88256AE0.00568638@boulder.ibm.com>; from Paul.McKenney@us.ibm.com on Tue, Oct 09, 2001 at 08:45:15AM -0700
On Tue, Oct 09, 2001 at 08:45:15AM -0700, Paul McKenney wrote:
> Please see the example above. I do believe that my algorithms are
> reliably forcing proper read ordering using IPIs, just in an different
> way.
I wasn't suggesting that the IPI wouldn't work -- it will.
But it will be _extremely_ slow.
I am suggesting that the lock-free algorithms should add the
read barriers, and that failure to do so indicates that they
are incomplete. If nothing else, it documents where the real
dependancies are.
r~
next prev parent reply other threads:[~2001-10-09 17:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 15:45 RFC: patch to allow lock-free traversal of lists with insertion Paul McKenney
2001-10-09 17:00 ` Richard Henderson [this message]
2001-10-10 3:33 ` Paul Mackerras
2001-10-10 17:02 ` Richard Henderson
2001-10-10 2:05 ` [Lse-tech] " Andrea Arcangeli
2001-10-10 5:05 ` Linus Torvalds
2001-10-10 5:17 ` BALBIR SINGH
2001-10-10 5:29 ` Davide Libenzi
2001-10-10 5:46 ` Linus Torvalds
2001-10-10 6:01 ` BALBIR SINGH
2001-10-10 15:23 ` Victor Yodaiken
2001-10-10 7:14 ` kdb requires kallsyms Kirill Ratkin
2001-10-10 7:38 ` BALBIR SINGH
2001-10-10 6:16 ` [Lse-tech] Re: RFC: patch to allow lock-free traversal of lists with insertion Paul Mackerras
2001-10-10 6:30 ` Linus Torvalds
2001-10-10 7:36 ` Paul Mackerras
2001-10-10 15:54 ` Victor Yodaiken
2001-10-10 21:56 ` Keith Owens
2001-10-10 22:24 ` Victor Yodaiken
2001-10-10 23:46 ` David S. Miller
2001-10-11 0:24 ` Davide Libenzi
2001-10-10 11:54 ` Keith Owens
2001-10-10 13:42 ` AIC7XXX war
2001-10-10 21:40 ` AIC7XXX Luigi Genoni
2001-10-10 13:24 ` [Lse-tech] Re: RFC: patch to allow lock-free traversal of lists with insertion Ivan Kokshaysky
2001-10-10 13:41 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2001-10-11 1:56 Paul E. McKenney
2001-10-12 4:14 ` Rusty Russell
2001-10-13 14:48 ` Paul E. McKenney
2001-10-10 21:47 Paul McKenney
2001-10-10 22:22 ` Richard Henderson
2001-10-10 22:27 ` Richard Henderson
2001-10-10 1:19 Paul McKenney
2001-10-10 1:43 ` Andrea Arcangeli
2001-10-09 18:01 Paul McKenney
2001-10-09 17:46 Paul McKenney
2001-10-09 16:51 Manfred Spraul
2001-10-09 15:28 Paul McKenney
2001-10-09 15:24 Paul McKenney
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 1:55 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
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=20011009100023.A27427@twiddle.net \
--to=rth@twiddle.net \
--cc=Paul.McKenney@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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