From: "Ross Biro" <rossb@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, mel@skynet.ie,
apm@shadoween.org
Subject: Re: [PATCH 1/2] MM: Make page tables relocatable -- conditional flush (rc9)
Date: Tue, 29 Apr 2008 09:27:53 -0400 [thread overview]
Message-ID: <d43160c70804290627g77a74e48k5a383dd441177293@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804161221060.14718@schroedinger.engr.sgi.com>
On Wed, Apr 16, 2008 at 3:22 PM, Christoph Lameter <clameter@sgi.com> wrote:
> The patch is interesting because it would allow the moving of page table
> pages into MOVABLE sections and reduce the size of the UNMOVABLE
> allocations signficantly (Ross: We need some numbers here). This in turn
Is there a standard test used to evaluate kernel memory fragmentation?
I'm sure I can rig up a test to create huge amounts of fragmentation
with about 1/2 the pages being page tables. However, I doubt that it
would reflect any real loads. Similarly, if I check the memory
fragmentation on my test system right after it's been booted, I won't
see much fragmentation and page tables won't be causing any trouble.
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:[~2008-04-29 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 16:39 [PATCH 1/2] MM: Make page tables relocatable -- conditional flush (rc9) Ross Biro
2008-04-14 22:57 ` Andrew Morton
2008-04-15 12:47 ` Ross Biro
2008-04-16 19:22 ` Christoph Lameter
2008-04-29 13:27 ` Ross Biro [this message]
2008-05-02 9:58 ` 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=d43160c70804290627g77a74e48k5a383dd441177293@mail.gmail.com \
--to=rossb@google.com \
--cc=akpm@linux-foundation.org \
--cc=apm@shadoween.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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).