linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	"mel@csn.ul.ie" <mel@csn.ul.ie>,
	"Zhao, Yakui" <yakui.zhao@intel.com>
Subject: Re: + memory-hotplug-migrate-swap-cache-page.patch added to -mm tree
Date: Tue, 30 Jun 2009 09:08:56 +0800	[thread overview]
Message-ID: <20090630010856.GE21254@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0906291813260.21956@gentwo.org>

Sorry, last mail sent to wrong list.

On Tue, Jun 30, 2009 at 06:13:54AM +0800, Christoph Lameter wrote:
> When does this occur? From user space you are typically not able to get to
> pages that are not mapped into your address space.
migrate.c has comments about this. swap readahead will make this happen too.

Thanks,
Shaohua
> >
> > The patch titled
> >      memory hotplug: migrate swap cache page
> > has been added to the -mm tree.  Its filename is
> >      memory-hotplug-migrate-swap-cache-page.patch
> >
> > Before you just go and hit "reply", please:
> >    a) Consider who else should be cc'ed
> >    b) Prefer to cc a suitable mailing list as well
> >    c) Ideally: find the original patch on the mailing list and do a
> >       reply-to-all to that, adding suitable additional cc's
> >
> > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> >
> > See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
> > out what to do about this
> >
> > The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
> >
> > ------------------------------------------------------
> > Subject: memory hotplug: migrate swap cache page
> > From: Shaohua Li <shaohua.li@intel.com>
> >
> > In test, some pages in swap-cache can't be migrated, as they aren't rmap.
> >
> > unmap_and_move() ignores swap-cache page which is just read in and hasn't
> > rmap (see the comments in the code), but swap_aops provides .migratepage.
> > Better to migrate such pages instead of ignore them.
> >
> > Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> > Cc: Mel Gorman <mel@csn.ul.ie>
> > Cc: Christoph Lameter <cl@linux-foundation.org>
> > Cc: Yakui Zhao <yakui.zhao@intel.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > ---
> >
> >  mm/migrate.c |    6 ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff -puN mm/migrate.c~memory-hotplug-migrate-swap-cache-page mm/migrate.c
> > --- a/mm/migrate.c~memory-hotplug-migrate-swap-cache-page
> > +++ a/mm/migrate.c
> > @@ -147,7 +147,7 @@ out:
> >  static void remove_file_migration_ptes(struct page *old, struct page *new)
> >  {
> >  	struct vm_area_struct *vma;
> > -	struct address_space *mapping = page_mapping(new);
> > +	struct address_space *mapping = new->mapping;
> >  	struct prio_tree_iter iter;
> >  	pgoff_t pgoff = new->index << (PAGE_CACHE_SHIFT - PAGE_SHIFT);
> >
> > @@ -664,13 +664,15 @@ static int unmap_and_move(new_page_t get
> >  			 *    needs to be effective.
> >  			 */
> >  			try_to_free_buffers(page);
> > +			goto rcu_unlock;
> >  		}
> > -		goto rcu_unlock;
> > +		goto skip_unmap;
> >  	}
> >
> >  	/* Establish migration ptes or remove ptes */
> >  	try_to_unmap(page, 1);
> >
> > +skip_unmap:
> >  	if (!page_mapped(page))
> >  		rc = move_to_new_page(newpage, page);
> >
> > _
> >
> > Patches currently in -mm which might be from shaohua.li@intel.com are
> >
> > linux-next.patch
> > memory-hotplug-update-zone-pcp-at-memory-online.patch
> > memory-hotplug-exclude-isolated-page-from-pco-page-alloc.patch
> > memory-hotplug-make-pages-from-movable-zone-always-isolatable.patch
> > memory-hotplug-alloc-page-from-other-node-in-memory-online.patch
> > memory-hotplug-migrate-swap-cache-page.patch
> >
> >

--
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:[~2009-06-30  1:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alpine.DEB.1.10.0906291813260.21956@gentwo.org>]

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=20090630010856.GE21254@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=yakui.zhao@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox