All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Rik van Riel <riel@redhat.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Mel Gorman <mel@csn.ul.ie>,
	Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: question on NUMA page migration
Date: Fri, 19 Oct 2012 18:39:02 +0200	[thread overview]
Message-ID: <1350664742.2768.40.camel@twins> (raw)
In-Reply-To: <5081777A.8050104@redhat.com>

On Fri, 2012-10-19 at 11:53 -0400, Rik van Riel wrote:
> 
> If we do need the extra refcount, why is normal
> page migration safe? :) 

Its mostly a matter of how convoluted you make the code, regular page
migration is about as bad as you can get

Normal does:

  follow_page(FOLL_GET) +1

  isolate_lru_page() +1

  put_page() -1

ending up with a page with a single reference (for anon, or one extra
each for the mapping and buffer).

And while I suppose I could do a put_page() in migrate_misplaced_page()
that makes the function frob the page-count depending on the return
value.

I always try and avoid conditional locks/refs, therefore the code ends
up doing:

  page = vm_normal_page()
  if (page) {
    get_page()

    migrate_misplaced_page()

    put_page()
  }


where migrate_misplaced_page() does isolate_lru_page()/putback_lru_page,
and this leaves the page-count invariant.

We got a ref, therefore we must put a ref, is easier than we got a ref
and must put except when...

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Rik van Riel <riel@redhat.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Mel Gorman <mel@csn.ul.ie>,
	Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: question on NUMA page migration
Date: Fri, 19 Oct 2012 18:39:02 +0200	[thread overview]
Message-ID: <1350664742.2768.40.camel@twins> (raw)
In-Reply-To: <5081777A.8050104@redhat.com>

On Fri, 2012-10-19 at 11:53 -0400, Rik van Riel wrote:
> 
> If we do need the extra refcount, why is normal
> page migration safe? :) 

Its mostly a matter of how convoluted you make the code, regular page
migration is about as bad as you can get

Normal does:

  follow_page(FOLL_GET) +1

  isolate_lru_page() +1

  put_page() -1

ending up with a page with a single reference (for anon, or one extra
each for the mapping and buffer).

And while I suppose I could do a put_page() in migrate_misplaced_page()
that makes the function frob the page-count depending on the return
value.

I always try and avoid conditional locks/refs, therefore the code ends
up doing:

  page = vm_normal_page()
  if (page) {
    get_page()

    migrate_misplaced_page()

    put_page()
  }


where migrate_misplaced_page() does isolate_lru_page()/putback_lru_page,
and this leaves the page-count invariant.

We got a ref, therefore we must put a ref, is easier than we got a ref
and must put except when...

  reply	other threads:[~2012-10-19 16:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 15:53 question on NUMA page migration Rik van Riel
2012-10-19 15:53 ` Rik van Riel
2012-10-19 16:39 ` Peter Zijlstra [this message]
2012-10-19 16:39   ` Peter Zijlstra
2012-10-19 17:13   ` Rik van Riel
2012-10-19 17:13     ` Rik van Riel
2012-10-19 17:53     ` Peter Zijlstra
2012-10-19 17:53       ` Peter Zijlstra
2012-10-19 18:33       ` Rik van Riel
2012-10-19 18:33         ` Rik van Riel
2012-10-20  1:23         ` Ingo Molnar
2012-10-20  1:23           ` Ingo Molnar
2012-10-20 16:02           ` Rik van Riel
2012-10-20 16:02             ` Rik van Riel
2012-10-21 12:30             ` Ingo Molnar
2012-10-21 12:30               ` Ingo Molnar
2012-10-21  2:39 ` Ni zhan Chen
2012-10-21  2:39   ` Ni zhan Chen
2012-10-21  2:40   ` Rik van Riel
2012-10-21  2:40     ` Rik van Riel
2012-10-21 12:31     ` Ingo Molnar
2012-10-21 12:31       ` Ingo Molnar

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=1350664742.2768.40.camel@twins \
    --to=peterz@infradead.org \
    --cc=aarcange@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mingo@kernel.org \
    --cc=riel@redhat.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 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.