mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: PageLRU can be non-atomic bit operation
Date: Mon, 23 Apr 2007 14:42:21 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704231438280.3516@blonde.wat.veritas.com> (raw)
In-Reply-To: <6.0.0.20.2.20070423210926.045668d0@172.19.0.2>

On Mon, 23 Apr 2007, Hisashi Hifumi wrote:
> >No.  The PG_lru flag bit is just one bit amongst many others:
> >what of concurrent operations changing other bits in that same
> >unsigned long e.g. trying to lock the page by setting PG_locked?
> >There are some places where such micro-optimizations can be made
> >(typically while first allocating the page); but in general, no.
> 
> In i386 and x86_64, btsl is used to change page flag. In this case, if btsl
> without lock prefix
> set PG_locked and PG_lru flag concurrently, does only one operation
> succeed ?

That's right: on an SMP machine, without the lock prefix, the operation
is no longer atomic: what's stored back may be missing the result of
one or the other of the racing operations.

Hugh

  reply	other threads:[~2007-04-23 13:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 10:54 Hisashi Hifumi
2007-04-23 11:16 ` Hugh Dickins
2007-04-23 12:34   ` Hisashi Hifumi
2007-04-23 13:42     ` Hugh Dickins [this message]
2007-04-24  1:54       ` Hisashi Hifumi
2007-04-24  2:29         ` KAMEZAWA Hiroyuki
2007-04-24  2:47         ` Nick Piggin
2007-04-24  8:12           ` Hisashi Hifumi
2007-04-24 10:13             ` Nick Piggin
2007-04-24 13:40         ` Hugh Dickins
2007-04-24 14:22           ` Andi Kleen
2007-04-25  8:56             ` Fernando Luis Vázquez Cao
2007-04-25  8:59               ` Andi Kleen

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=Pine.LNX.4.64.0704231438280.3516@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=akpm@linux-foundation.org \
    --cc=hifumi.hisashi@oss.ntt.co.jp \
    --cc=linux-kernel@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 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®