From: Ingo Molnar <mingo@elte.hu>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ravikiran G Thirumalai <kiran@scalex86.org>
Subject: Re: [rfc][patch] queued spinlocks (i386)
Date: Sat, 24 Mar 2007 18:29:59 +0100 [thread overview]
Message-ID: <20070324172959.GB542@elte.hu> (raw)
In-Reply-To: <17925.18904.820106.145029@gargle.gargle.HOWL>
* Nikita Danilov <nikita@clusterfs.com> wrote:
> Indeed, this technique is very well known. E.g.,
> http://citeseer.ist.psu.edu/anderson01sharedmemory.html has a whole
> section (3. Local-spin Algorithms) on them, citing papers from the
> 1990 onward.
that is a cool reference! So i'd suggest to do (redo?) the patch based
on those concepts and that terminology and not use 'queued spinlocks'
that are commonly associated with MS's stuff. And as a result the
contended case would be optimized some more via local-spin algorithms.
(which is not a key thing for us, but which would be nice to have
nevertheless)
Ingo
next prev parent reply other threads:[~2007-03-24 17:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 8:59 Nick Piggin
2007-03-23 9:40 ` Eric Dumazet
2007-03-23 9:59 ` Nick Piggin
2007-03-23 19:27 ` Ravikiran G Thirumalai
2007-03-23 10:04 ` Ingo Molnar
2007-03-23 10:10 ` Nick Piggin
2007-03-23 16:48 ` Parag Warudkar
2007-03-23 18:15 ` Davide Libenzi
2007-03-23 10:32 ` Nick Piggin
2007-03-23 10:40 ` Eric Dumazet
2007-03-23 11:02 ` William Lee Irwin III
2007-03-24 15:55 ` Nikita Danilov
2007-03-24 17:29 ` Ingo Molnar [this message]
2007-03-24 18:49 ` Nikita Danilov
2007-03-28 6:43 ` Nick Piggin
2007-03-28 19:26 ` Davide Libenzi
2007-03-28 22:00 ` Davide Libenzi
2007-03-29 1:36 ` Nick Piggin
2007-03-29 7:16 ` Nick Piggin
2007-03-30 0:27 ` Davide Libenzi
2007-03-30 1:59 ` Nick Piggin
2007-03-30 2:43 ` Davide Libenzi
2007-03-29 1:24 ` Nick Piggin
2007-03-24 21:41 ` Andrew Morton
2007-03-28 6:56 ` Nick Piggin
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=20070324172959.GB542@elte.hu \
--to=mingo@elte.hu \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@clusterfs.com \
--cc=npiggin@suse.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
all inboxes | Powered by JetHome®