All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [RFC] recursive pagetables for x86 PAE
Date: 14 Jun 2003 10:49:57 -0700	[thread overview]
Message-ID: <1055612996.3531.3270.camel@nighthawk> (raw)
In-Reply-To: <200306141327.48649.oliver@neukum.org>

On Sat, 2003-06-14 at 04:27, Oliver Neukum wrote:
> Am Freitag, 13. Juni 2003 23:47 schrieb Dave Hansen:
> > The following patches implement something which we like to call UKVA.
> > It's a Kernel Virtual Area which is private to a process, just like
> > Userspace.  You can put any process-local data that you want in the
> > area.  But, for now, I just put PTE pages in there.
> 
> If you put only such pages there, do you really want that memory to
> be per task? IMHO it should be per memory context to aid threading
> performance.

I think you're confusing what I mean by tasks and processes.  A task is
something with a task_struct and a kernel stack.  A process is a single
task, or multiple tasks that share an mm.   If things share an mm, they
share pagetables implicitly.  Per-process _is_  per memory context.

> Secondly, doesn't this scream for using large pages?

Large pages aren't used for generic user memory at all.  That would take
some serious surgery.  (Don't get Bill started on it :)

-- 
Dave Hansen
haveblue@us.ibm.com


WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [RFC] recursive pagetables for x86 PAE
Date: 14 Jun 2003 10:49:57 -0700	[thread overview]
Message-ID: <1055612996.3531.3270.camel@nighthawk> (raw)
In-Reply-To: <200306141327.48649.oliver@neukum.org>

On Sat, 2003-06-14 at 04:27, Oliver Neukum wrote:
> Am Freitag, 13. Juni 2003 23:47 schrieb Dave Hansen:
> > The following patches implement something which we like to call UKVA.
> > It's a Kernel Virtual Area which is private to a process, just like
> > Userspace.  You can put any process-local data that you want in the
> > area.  But, for now, I just put PTE pages in there.
> 
> If you put only such pages there, do you really want that memory to
> be per task? IMHO it should be per memory context to aid threading
> performance.

I think you're confusing what I mean by tasks and processes.  A task is
something with a task_struct and a kernel stack.  A process is a single
task, or multiple tasks that share an mm.   If things share an mm, they
share pagetables implicitly.  Per-process _is_  per memory context.

> Secondly, doesn't this scream for using large pages?

Large pages aren't used for generic user memory at all.  That would take
some serious surgery.  (Don't get Bill started on it :)

-- 
Dave Hansen
haveblue@us.ibm.com

--
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:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-06-14 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 21:47 [RFC] recursive pagetables for x86 PAE Dave Hansen
2003-06-14 11:27 ` Oliver Neukum
2003-06-14 11:27   ` Oliver Neukum
2003-06-14 13:49   ` William Lee Irwin III
2003-06-14 13:49     ` William Lee Irwin III
2003-06-14 17:49   ` Dave Hansen [this message]
2003-06-14 17:49     ` Dave Hansen

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=1055612996.3531.3270.camel@nighthawk \
    --to=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.com \
    --cc=oliver@neukum.org \
    --cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.