mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert Cahalan" <acahalan@gmail.com>
To: "Mikulas Patocka" <mikulas@artax.karlin.mff.cuni.cz>
Cc: "Pavel Machek" <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: 2048 CPUs [was: Re: New filesystem for Linux]
Date: Tue, 14 Nov 2006 01:24:29 -0500	[thread overview]
Message-ID: <787b0d920611132224n76cb2345t685bb5c521cedcbc@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611122103060.4965@artax.karlin.mff.cuni.cz>

> >> No intel document guarantees you that if more CPUs
> >> simultaneously execute locked cmpxchg in a loop that a
> >
> > If we are talking 2048 cpus, we are talking ia64.
>
> IA64 spinlock is locked cmpxchg, if failed than pause (i386 equivalent of
> rep nop) read the value, and if unlocked, try cmpxchg again.
>
> There is no fairness in it.

I suppose we could use something better.

There is the MCS lock, the related CLH lock, and IBM's
improvement on the MCS lock. As with RCU, we'd need
to get IBM's permission to use their lock. (so, how did we
get permission for RCU?) The basic MCS lock is also
patented I think.

http://www.cs.rochester.edu/~scott/professional/Dijkstra/presentation.html

  reply	other threads:[~2006-11-14  6:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <787b0d920611041154l69db46abv4c8c467809ada57c@mail.gmail.com>
2006-11-04 22:36 ` Mikulas Patocka
     [not found]   ` <787b0d920611050802o460a4000r5ce154e589732a02@mail.gmail.com>
2006-11-06  1:47     ` Mikulas Patocka
2006-11-07 21:26   ` Pavel Machek
2006-11-07 22:36     ` Mikulas Patocka
2006-11-07 23:14       ` Pavel Machek
2006-11-08 18:26         ` Mikulas Patocka
2006-11-10  9:03           ` Pavel Machek
2006-11-10 15:20             ` Mikulas Patocka
2006-11-10 16:20               ` Alan Cox
2006-11-12 14:28               ` Pavel Machek
2006-11-12 20:07                 ` Mikulas Patocka
2006-11-14  6:24                   ` Albert Cahalan [this message]
2006-11-08  3:04   ` David Chinner

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=787b0d920611132224n76cb2345t685bb5c521cedcbc@mail.gmail.com \
    --to=acahalan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikulas@artax.karlin.mff.cuni.cz \
    --cc=pavel@ucw.cz \
    /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®