From: Nick Piggin <npiggin@suse.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hugh Dickins <hugh@veritas.com>, Andrew Morton <akpm@osdl.org>,
Andrea Arcangeli <andrea@suse.de>,
Linus Torvalds <torvalds@osdl.org>,
David Miller <davem@davemloft.net>
Subject: Re: [patch 3/3] mm: PageActive no testset
Date: Thu, 19 Jan 2006 15:50:08 +0100 [thread overview]
Message-ID: <20060119145008.GA20126@wotan.suse.de> (raw)
In-Reply-To: <20060118141346.GB7048@dmt.cnet>
Hi Marcelo,
On Wed, Jan 18, 2006 at 12:13:46PM -0200, Marcelo Tosatti wrote:
> Hi Nick,
>
> On Wed, Jan 18, 2006 at 11:40:58AM +0100, Nick Piggin wrote:
> > PG_active is protected by zone->lru_lock, it does not need TestSet/TestClear
> > operations.
>
> page->flags bits (including PG_active and PG_lru bits) are touched by
> several codepaths which do not hold zone->lru_lock.
>
> AFAICT zone->lru_lock guards access to the LRU list, and no more than
> that.
>
Yep.
> Moreover, what about consistency of the rest of page->flags bits?
>
That's OK, set_bit and clear_bit are atomic as well, they just don't
imply memory barriers and can be implemented a bit more simply.
The test-set / test-clear operations also kind of imply that it is
being used for locking or without other synchronisation (usually).
> PPC for example implements test_and_set_bit() with:
>
> lwarx reg, addr (load and create reservation for 32-bit addr)
> or reg, BITOP_MASK(nr)
> stwcx reg, addr (store word upon reservation validation, otherwise loop)
>
Thanks,
Nick
next prev parent reply other threads:[~2006-01-19 14:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 10:40 [patch 0/4] mm: de-skew page refcount Nick Piggin
2006-01-18 10:40 ` [patch 1/4] mm: page refcount use atomic primitives Nick Piggin
2006-01-18 10:40 ` [patch 2/4] mm: PageLRU no testset Nick Piggin
2006-01-19 17:48 ` Nikita Danilov
2006-01-19 18:10 ` Nick Piggin
2006-01-18 10:40 ` [patch 3/3] mm: PageActive " Nick Piggin
2006-01-18 14:13 ` Marcelo Tosatti
2006-01-19 14:50 ` Nick Piggin [this message]
2006-01-19 16:52 ` Marcelo Tosatti
2006-01-19 20:02 ` Nick Piggin
2006-01-19 21:41 ` Marcelo Tosatti
2006-01-18 10:41 ` [patch 4/4] mm: less atomic ops Nick Piggin
2006-01-18 16:38 ` [patch 0/4] mm: de-skew page refcount Linus Torvalds
2006-01-18 17:05 ` Nick Piggin
2006-01-18 19:27 ` Linus Torvalds
2006-01-19 14:00 ` Nick Piggin
2006-01-19 16:36 ` Linus Torvalds
2006-01-19 17:06 ` Nick Piggin
2006-01-19 17:27 ` Linus Torvalds
2006-01-19 17:38 ` Nick Piggin
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=20060119145008.GA20126@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=davem@davemloft.net \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).