linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Ross Biro <rossb@google.com>
Cc: linux-mm@kvack.org, Mel Gorman <MELGOR@ie.ibm.com>
Subject: Re: RFC/POC Make Page Tables Relocatable
Date: Thu, 25 Oct 2007 13:00:19 -0700	[thread overview]
Message-ID: <1193342419.24087.71.camel@localhost> (raw)
In-Reply-To: <d43160c70710251253j2f4e640uc0ccc0432738f55c@mail.gmail.com>

On Thu, 2007-10-25 at 15:53 -0400, Ross Biro wrote:
> On 10/25/07, Dave Hansen <haveblue@us.ibm.com> wrote:
> > My guys says that this is way too complicated to be pursued in this
> > form.  But, don't listen to me.  You don't have to convince _me_.
> 
> At this point, I'm more interested if anyone has any objections in
> principle to the overall thing.  If so, and they are legitimate, then
> it's not worth pursuing.  If not, then I'll start.  However, I
> disagree with your order.

Me too!  I just ran through your patch and wrote ideas as I saw them in
your patch order.  I bet they need to be done in much different orders
in reality. 

> I'm thinking more like:
> 
> 1) Support for relocation.

Generic slab relocation, right?

> 2) Support for handles

I've heard these handles are more or less what some other UNIXes do.
That doesn't give it points in my book.  :)

> 3) Test module.
> 
> These three work together and give a framework for validating the
> relocation code with out causing too much trouble.  The only problem
> is that they are mostly useless on their own.

Useless on their own is actually OK.  Patches series are often useless
up until patch 943/943.

> Then the page table related code, using your suggestion above
> (provided I can get it to work.  I'm worried about the page table
> being freed while I'm trying to figure out what mm it belongs to.)
> I'll break this into small chunks.

How would it get freed?

-- Dave

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

  parent reply	other threads:[~2007-10-25 20:00 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 [this message]
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
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=1193342419.24087.71.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=MELGOR@ie.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=rossb@google.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;
as well as URLs for NNTP newsgroup(s).