All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: write_unlock: replace clear_bit with byte store
Date: Fri, 29 Apr 2005 11:37:25 +0000	[thread overview]
Message-ID: <17010.7285.561402.280478@napali.hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504281329150.23584@schroedinger.engr.sgi.com>

>>>>> On Thu, 28 Apr 2005 13:53:11 -0700 (PDT), Christoph Lameter <clameter@engr.sgi.com> said:

  Christoph> I thought that a memory barrier was needed to insure that
  Christoph> the clearing of the lock becomes visible after changes
  Christoph> done in the critical section?

With "volatile", the compiler will generate stX.rel...

  Christoph> y is defined in its own block.

Ummh, macros 101: think about what happens for _raw_write_unlock(y)...

	--david

  parent reply	other threads:[~2005-04-29 11:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 20:32 write_unlock: replace clear_bit with byte store Christoph Lameter
2005-04-28 20:43 ` David Mosberger
2005-04-28 20:53 ` Christoph Lameter
2005-04-28 22:05 ` Christoph Lameter
2005-04-28 22:25 ` Zou, Nanhai
2005-04-28 22:51 ` Christoph Lameter
2005-04-28 23:55 ` Chen, Kenneth W
2005-04-29  0:21 ` Christoph Lameter
2005-04-29  0:28 ` Chen, Kenneth W
2005-04-29  0:50 ` Christoph Lameter
2005-04-29  1:04 ` Chen, Kenneth W
2005-04-29  1:48 ` Chen, Kenneth W
2005-04-29  7:09 ` David Mosberger
2005-04-29 11:37 ` David Mosberger [this message]
2005-04-29 15:19 ` Christoph Lameter
2005-04-29 15:20 ` Christoph Lameter
2005-04-29 15:24 ` David Mosberger
2005-04-29 15:28 ` David Mosberger
2005-04-29 15:30 ` Christoph Lameter
2005-04-29 15:38 ` David Mosberger
2005-04-29 15:46 ` Christoph Lameter
2005-04-29 15:48 ` David Mosberger
2005-04-29 15:51 ` Christoph Hellwig
2005-04-29 15:55 ` Christoph Lameter
2005-04-29 16:01 ` David Mosberger

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=17010.7285.561402.280478@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.