From: Mel Gorman <mel@csn.ul.ie>
To: Matt Mackall <mpm@selenic.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Avoiding fragmentation through different allocator
Date: Thu, 13 Jan 2005 10:22:13 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.58.0501131011390.31154@skynet> (raw)
In-Reply-To: <20050113070314.GL2995@waste.org>
On Wed, 12 Jan 2005, Matt Mackall wrote:
> On Wed, Jan 12, 2005 at 09:09:24PM +0000, Mel Gorman wrote:
> > I stress-tested this patch very heavily and it never oopsed so I am
> > confident of it's stability, so what is left is to look at the results of
> > this patch were and I think they look promising in a number of respects. I
> > have graphs that do not translate to text very well, so I'll just point you
> > to http://www.csn.ul.ie/~mel/projects/mbuddy-results-1 instead.
>
> This graph rather hard to comprehend.
>
There is not a lot of ways to illustrate how pages are allocated
throughout an address space. If you have a better suggestion, I can update
the relevant tool.
> > The results were not spectacular but still very interesting. Under heavy
> > stresing (updatedb + 4 simultaneous -j4 kernel compiles with avg load 15)
> > fragmentation is consistently lower than the standard allocator. It could
> > also be a lot better if there was some means of purging caches, userpages
> > and buffers but thats in the future. For the moment, the only real control
> > I had was the buffer pages.
>
> You might stress higher order page allocation with a) 8k stacks turned
> on b) UDP NFS with large read/write.
>
CONFIG_4KSTACKS is not set on my system so I'm already using 8k stacks.
Based on Trond's mail, I checked my network and the MTU is 1500 bytes so I
don't think I can force high-order allocations there.
Also, while I agree this test would be important, I think it'll be way
more important when there is something in place that actually tries to
free up high-order blocks and then compare.
--
Mel Gorman
next prev parent reply other threads:[~2005-01-13 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 21:09 [RFC] Avoiding fragmentation through different allocator Mel Gorman
2005-01-13 7:03 ` Matt Mackall
2005-01-13 7:20 ` Trond Myklebust
2005-01-13 10:22 ` Mel Gorman [this message]
2005-01-13 7:31 ` William Lee Irwin III
2005-01-13 10:11 ` Mel Gorman
2005-01-14 21:42 ` Marcelo Tosatti
2005-01-15 1:31 ` William Lee Irwin III
2005-01-15 19:19 ` Mel Gorman
2005-01-12 22:45 Tolentino, Matthew E
2005-01-12 23:12 ` Mel Gorman
2005-01-13 8:02 ` Hirokazu Takahashi
2005-01-13 10:27 ` Mel Gorman
2005-01-16 4:03 ` Yasunori Goto
2005-01-16 16:21 ` Mel Gorman
2005-01-17 23:08 ` Yasunori Goto
2005-01-19 13:45 ` Mel Gorman
2005-01-17 16:48 Tolentino, Matthew E
2005-01-19 13:17 ` 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=Pine.LNX.4.58.0501131011390.31154@skynet \
--to=mel@csn.ul.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.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).