From: Oliver Neukum <oliver@neukum.org>
To: Dave Hansen <haveblue@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [RFC] recursive pagetables for x86 PAE
Date: Sat, 14 Jun 2003 13:27:48 +0200 [thread overview]
Message-ID: <200306141327.48649.oliver@neukum.org> (raw)
In-Reply-To: <1055540875.3531.2581.camel@nighthawk>
Am Freitag, 13. Juni 2003 23:47 schrieb Dave Hansen:
> When you have lots of tasks, the pagetables start taking up lots of
> lowmem. We have the ability to push the PTE pages into highmem, but
> that exacts a penalty from the atomic kmaps which, depending on
> workload, can be a 10-15% performance hit.
>
> 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.
Secondly, doesn't this scream for using large pages?
Regards
Oliver
--
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>
next prev parent reply other threads:[~2003-06-14 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 21:47 Dave Hansen
2003-06-14 11:27 ` Oliver Neukum [this message]
2003-06-14 13:49 ` William Lee Irwin III
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=200306141327.48649.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox