All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: Nick Piggin <npiggin@suse.de>, 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>,
	Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: [patch 2/4] mm: PageLRU no testset
Date: Thu, 19 Jan 2006 19:10:07 +0100	[thread overview]
Message-ID: <20060119181007.GC6564@wotan.suse.de> (raw)
In-Reply-To: <17359.53508.481749.294382@gargle.gargle.HOWL>

On Thu, Jan 19, 2006 at 08:48:52PM +0300, Nikita Danilov wrote:
> Nick Piggin writes:
>  > PG_lru is protected by zone->lru_lock. It does not need TestSet/TestClear
>  > operations.
>  > 
>  > Signed-off-by: Nick Piggin <npiggin@suse.de>
>  > 
>  > Index: linux-2.6/mm/vmscan.c
>  > ===================================================================
>  > --- linux-2.6.orig/mm/vmscan.c
>  > +++ linux-2.6/mm/vmscan.c
>  > @@ -775,9 +775,10 @@ int isolate_lru_page(struct page *page)
>  >  	if (PageLRU(page)) {
>  >  		struct zone *zone = page_zone(page);
>  >  		spin_lock_irq(&zone->lru_lock);
>  > -		if (TestClearPageLRU(page)) {
>  > +		if (PageLRU(page)) {
>  >  			ret = 1;
>  >  			get_page(page);
>  > +			ClearPageLRU(page);
> 
> Why is that better? ClearPageLRU() is also "atomic" operation (in the
> sense of using LOCK_PREFIX on x86), so it seems this change strictly
> adds cycles to the hot-path when page is on LRU.
> 

Less restrictive memory ordering requirements.

Nick
 

  reply	other threads:[~2006-01-19 18:10 UTC|newest]

Thread overview: 41+ 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 ` Nick Piggin
2006-01-18 10:40 ` [patch 1/4] mm: page refcount use atomic primitives Nick Piggin
2006-01-18 10:40   ` Nick Piggin
2006-01-18 10:40 ` [patch 2/4] mm: PageLRU no testset Nick Piggin
2006-01-18 10:40   ` Nick Piggin
2006-01-19 17:48   ` Nikita Danilov
2006-01-19 18:10     ` Nick Piggin [this message]
2006-01-18 10:40 ` [patch 3/3] mm: PageActive " Nick Piggin
2006-01-18 10:40   ` Nick Piggin
2006-01-18 14:13   ` Marcelo Tosatti
2006-01-18 14:13     ` Marcelo Tosatti
2006-01-19 14:50     ` Nick Piggin
2006-01-19 14:50       ` Nick Piggin
2006-01-19 16:52       ` Marcelo Tosatti
2006-01-19 16:52         ` Marcelo Tosatti
2006-01-19 20:02         ` Nick Piggin
2006-01-19 20:02           ` Nick Piggin
2006-01-19 21:41           ` Marcelo Tosatti
2006-01-19 21:41             ` Marcelo Tosatti
2006-01-18 10:41 ` [patch 4/4] mm: less atomic ops Nick Piggin
2006-01-18 10:41   ` Nick Piggin
2006-01-18 16:38 ` [patch 0/4] mm: de-skew page refcount Linus Torvalds
2006-01-18 16:38   ` Linus Torvalds
2006-01-18 17:05   ` Nick Piggin
2006-01-18 17:05     ` Nick Piggin
2006-01-18 19:27     ` Linus Torvalds
2006-01-18 19:27       ` Linus Torvalds
2006-01-19 14:00       ` Nick Piggin
2006-01-19 14:00         ` Nick Piggin
2006-01-19 16:36         ` Linus Torvalds
2006-01-19 16:36           ` Linus Torvalds
2006-01-19 17:06           ` Nick Piggin
2006-01-19 17:06             ` Nick Piggin
2006-01-19 17:27             ` Linus Torvalds
2006-01-19 17:27               ` Linus Torvalds
2006-01-19 17:38               ` Nick Piggin
2006-01-19 17:38                 ` Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2006-01-08  5:23 [patch 0/4] mm: de-skew page_count Nick Piggin
2006-01-08  5:20 ` [patch 2/4] mm: PageLRU no testset Nick Piggin
2006-01-08  5:24   ` Nick Piggin
2005-12-05 11:59 [patch 0/4] mm: optimisations Nick Piggin
2005-12-05 11:59 ` [patch 2/4] mm: PageLRU no testset 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=20060119181007.GC6564@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=davem@davemloft.net \
    --cc=hugh@veritas.com \
    --cc=nikita@clusterfs.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 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.