linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Lee Schermerhorn <lee.schermerhorn@hp.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH/RFC] AutoPage Migration - V0.1 - 1/8 migrate task memory with default policy
Date: Mon, 13 Mar 2006 15:52:06 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0603131547020.13713@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1142019479.5204.15.camel@localhost.localdomain>

On Fri, 10 Mar 2006, Lee Schermerhorn wrote:

> +/*
> + * Migrate all eligible pages mapped in vma NOT on destination node to
> + * the destination node.
> + * Returns error or the number of pages not migrated.
> + */
> +static int migrate_vma_to_node(struct vm_area_struct *vma, int dest, int flags)
> +{

This duplicates code in migrate_to_node().

> +/*
> + * for filtering 'no access' segments
> +TODO:  what are these?

??

> +	down_read(&mm->mmap_sem);
> +	for (vma = mm->mmap; vma; vma = vma->vm_next) {
> +		struct mempolicy *pol = get_vma_policy(current, vma,
> +							 vma->vm_start);
> +		int err;
> +
> +		if (pol->policy != MPOL_DEFAULT)
> +			continue;
> +		if (vma_no_access(vma))
> +			continue;
> +
> +		// TODO:  more eligibility filtering?
> +
> +		// TODO:  more agressive migration ['MOVE_ALL] ?
> +		//        via sysctl?
> +		err = migrate_vma_to_node(vma, dest, MPOL_MF_MOVE);
> +
> +	}

Duplicates code in migrate_to_node().

Could you add some special casing instead to migrate_to_node and/or 
check_range?

--
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:[~2006-03-13 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 19:37 Lee Schermerhorn
2006-03-13 23:52 ` Christoph Lameter [this message]
2006-03-14 14:46   ` Lee Schermerhorn
2006-03-14 15:36     ` Christoph Lameter

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.0603131547020.13713@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=lee.schermerhorn@hp.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