linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: page migration: Only migrate pages if allocation in the highest zone is possible
Date: Tue, 1 May 2007 14:07:11 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705011405440.12797@blonde.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704301210580.7691@schroedinger.engr.sgi.com>

On Mon, 30 Apr 2007, Christoph Lameter wrote:
> 
> page migration: Only migrate pages if allocation in the highest zone is possible
> 
> Address spaces contain an allocation flag that specifies restriction on
> the zone for pages placed in the mapping. I.e. some device may require pages
> to be allocated from a DMA zone. Block devices may not be able to use pages
> from HIGHMEM.
> 
> Memory policies and the common use of page migration works only on the
> highest zone. If the address space does not allow allocation from the
> highest zone then the pages in the address space are not migratable simply
> because we can only allocate memory for a specified node if we allow
> allocation for the highest zone on each node.
> 
> Cc: Hugh Dickins <hugh@veritas.com>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>

Thanks, Christoph:
Acked-by: Hugh Dickins <hugh@veritas.com>

> 
> ---
>  include/linux/migrate.h |   11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> Index: linux-2.6.21-rc7-mm2/include/linux/migrate.h
> ===================================================================
> --- linux-2.6.21-rc7-mm2.orig/include/linux/migrate.h	2007-04-29 23:58:47.000000000 -0700
> +++ linux-2.6.21-rc7-mm2/include/linux/migrate.h	2007-04-30 12:18:41.000000000 -0700
> @@ -2,6 +2,8 @@
>  #define _LINUX_MIGRATE_H
>  
>  #include <linux/mm.h>
> +#include <linux/mempolicy.h>
> +#include <linux/pagemap.h>
>  
>  typedef struct page *new_page_t(struct page *, unsigned long private, int **);
>  
> @@ -10,6 +12,15 @@ static inline int vma_migratable(struct 
>  {
>  	if (vma->vm_flags & (VM_IO|VM_HUGETLB|VM_PFNMAP|VM_RESERVED))
>  		return 0;
> +	/*
> +	 * Migration allocates pages in the highest zone. If we cannot
> +	 * do so then migration (at least from node to node) is not
> +	 * possible.
> +	 */
> +	if (vma->vm_file &&
> +		gfp_zone(mapping_gfp_mask(vma->vm_file->f_mapping))
> +								< policy_zone)
> +			return 0;
>  	return 1;
>  }
>  

--
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>

      reply	other threads:[~2007-05-01 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30  6:17 Christoph Lameter
2007-04-30 11:58 ` Hugh Dickins
2007-04-30 19:20   ` Christoph Lameter
2007-05-01 13:07     ` Hugh Dickins [this message]

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.0705011405440.12797@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.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