From: "Ross Biro" <rossb@google.com>
To: Mel Gorman <mel@skynet.ie>
Cc: Dave Hansen <haveblue@us.ibm.com>,
linux-mm@kvack.org, Mel Gorman <MELGOR@ie.ibm.com>
Subject: Re: RFC/POC Make Page Tables Relocatable
Date: Fri, 26 Oct 2007 12:51:38 -0400 [thread overview]
Message-ID: <d43160c70710260951q351a6864ye5bb49e1b8a96aa3@mail.gmail.com> (raw)
In-Reply-To: <20071026161007.GA19443@skynet.ie>
On 10/26/07, Mel Gorman <mel@skynet.ie> wrote:
> I suspect this might be overkill from a memory fragmentation
> perspective. When grouping pages by mobility, page table pages are
> currently considered MIGRATE_UNMOVABLE. From what I have seen, they are
I may be being dense, but the page migration code looks to me like it
just moves pages in a process from one node to another node with no
effort to touch the page tables. It would be easy to hook the code I
wrote into the page migration code, what I don't understand is when
the page tables should be migrated? Only when the whole process is
being migrated? When all the pages pointed to a page table are being
migrated? When any page pointed to by the page table is being
migrated?
Ross
--
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>
next prev parent reply other threads:[~2007-10-26 16:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 15:16 RFC/POC Make Page Tables Relocatable Ross Biro
2007-10-25 16:46 ` Dave Hansen
2007-10-25 17:40 ` Ross Biro
2007-10-25 18:08 ` Dave Hansen
2007-10-25 18:44 ` Ross Biro
2007-10-25 18:47 ` Dave Hansen
2007-10-25 19:23 ` Dave Hansen
2007-10-25 19:53 ` Ross Biro
2007-10-25 19:56 ` Dave Hansen
2007-10-25 19:58 ` Ross Biro
2007-10-25 20:15 ` Dave Hansen
2007-10-25 20:00 ` Dave Hansen
2007-10-25 20:10 ` Ross Biro
2007-10-25 20:20 ` Dave Hansen
2007-10-26 16:10 ` Mel Gorman
2007-10-26 16:51 ` Ross Biro [this message]
2007-10-26 17:11 ` Mel Gorman
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=d43160c70710260951q351a6864ye5bb49e1b8a96aa3@mail.gmail.com \
--to=rossb@google.com \
--cc=MELGOR@ie.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
/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;
as well as URLs for NNTP newsgroup(s).