From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: sct@dcs.ed.ac.uk
Cc: torvalds@transmeta.com, linux-mm@kvack.org, linux-smp@vger.rutgers.edu
Subject: Re: Lazy page reclamation on SMP machines: memory barriers
Date: Tue, 24 Mar 1998 15:45:21 -0800 [thread overview]
Message-ID: <199803242345.PAA02702@dm.cobaltmicro.com> (raw)
In-Reply-To: <199803242254.WAA03274@dax.dcs.ed.ac.uk> (sct@dcs.ed.ac.uk)
Date: Tue, 24 Mar 1998 22:54:18 GMT
From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
> Intel guarantees total ordering around any locked instruction, so
> the spinlocks themselves act as the barriers.
Fine. Can we assume that spinlocks and atomic set/clear_bit
instructions have the same semantics on other CPUs?
Yes, you certainly can for spinlocks.
Later,
David S. Miller
davem@dm.cobaltmicro.com
next prev parent reply other threads:[~1998-03-24 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-23 22:49 Stephen C. Tweedie
1998-03-23 23:20 ` Linus Torvalds
1998-03-24 22:54 ` Stephen C. Tweedie
1998-03-24 23:45 ` David S. Miller [this message]
1998-03-25 0:11 ` Linus Torvalds
1998-03-25 9:08 ` Rik van Riel
1998-03-23 23:37 ` Linus Torvalds
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=199803242345.PAA02702@dm.cobaltmicro.com \
--to=davem@dm.cobaltmicro.com \
--cc=linux-mm@kvack.org \
--cc=linux-smp@vger.rutgers.edu \
--cc=sct@dcs.ed.ac.uk \
--cc=torvalds@transmeta.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