public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: carlos@systemhalted.org
Cc: drow@false.org, joseph@codesourcery.com, schwab@linux-m68k.org,
	thomas_schwinge@mentor.com, kkojima@rr.iij4u.or.jp,
	marcus.shawcroft@linaro.org, katsuki.uwatoko@toshiba.co.jp,
	libc-ports@sourceware.org
Subject: Re: [PATCH] Avoid unnecessary busy loop in __lll_timedlock_wait on ARM.
Date: Sat, 09 Feb 2013 06:49:00 -0000	[thread overview]
Message-ID: <20130209.014909.573423212502453699.davem@davemloft.net> (raw)
In-Reply-To: <CAE2sS1isYziYbmy1sgvhVPTp8_3hbNYKsnj_pXrZmjv53=mm6Q@mail.gmail.com>

From: "Carlos O'Donell" <carlos@systemhalted.org>
Date: Fri, 8 Feb 2013 23:18:42 -0500

> I see that sparc32 also has a unique copy of lowlevellock.c Why the
> use of *_24_* atomic primitives? Faster?

On pre-v9 32-bit sparc, we lack any usable atomic compare and
swap.

All we have is an 8-bit spinlock.

So we implement things in a 32-bit word which is composed of a 24-bit
counter and an 8-bit lock.

  reply	other threads:[~2013-02-09  6:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  8:42 katsuki.uwatoko
2013-02-07 23:33 ` Joseph S. Myers
2013-02-08  0:13   ` katsuki.uwatoko
2013-02-09  4:18   ` Carlos O'Donell
2013-02-09  6:49     ` David Miller [this message]
2013-02-09 14:56       ` Carlos O'Donell
2013-02-10  4:56         ` David Miller
2013-02-10 17:55           ` Carlos O'Donell
2013-02-12 21:41             ` Daniel Jacobowitz
2013-02-12 21:41               ` Daniel Jacobowitz
2013-02-12 21:57               ` Carlos O'Donell

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=20130209.014909.573423212502453699.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=carlos@systemhalted.org \
    --cc=drow@false.org \
    --cc=joseph@codesourcery.com \
    --cc=katsuki.uwatoko@toshiba.co.jp \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=libc-ports@sourceware.org \
    --cc=marcus.shawcroft@linaro.org \
    --cc=schwab@linux-m68k.org \
    --cc=thomas_schwinge@mentor.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).