From: William Lee Irwin III <wli@holomorphy.com>
To: Jason Papadopoulos <jasonp@boo.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rewritten page coloring for 2.4.20 kernel
Date: Sat, 4 Jan 2003 21:07:55 -0800 [thread overview]
Message-ID: <20030105050755.GH9704@holomorphy.com> (raw)
In-Reply-To: <3.0.6.32.20030104233111.007ed3c0@boo.net>
On Sat, Jan 04, 2003 at 11:31:11PM -0500, Jason Papadopoulos wrote:
> Hello. After a year in stasis, I've completely rebuilt my kernel
> patch that implements page coloring. Improvements include:
> - Page coloring is now hardwired into the kernel. The hash
> queues now use bootmem, and page coloring is always on. The
> patch still creates /proc/page_color for statistics, but that
> will go away in time.
> - Automatic detection of external cache size on many architectures.
> I have no idea if any of this code works, since I don't have any
> of the target machines. The preferred way to initialize the coloring
> is by passing "page_color=<external cache size in kB>" as a boot
> argument.
> - NUMA-safe, discontig-safe
> Right now the actual page coloring algorithm is the same as in previous
> patches, and performs the same. In the next few weeks I'll be trying new
> ideas that will hopefully reduce fragmentation and increase performance.
> This is an early attempt to get some feedback on mistakes I may have made.
Any chance for a 2.5.x-mm port? This is a bit feature-ish for 2.4.x.
Thanks,
Bill
--
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/
next prev parent reply other threads:[~2003-01-05 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 4:31 Jason Papadopoulos
2003-01-05 5:07 ` William Lee Irwin III [this message]
2003-01-05 16:03 jasonp
2003-01-05 19:34 ` William Lee Irwin III
2003-01-05 20:04 ` Jason Papadopoulos
2003-01-05 20:45 ` William Lee Irwin III
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=20030105050755.GH9704@holomorphy.com \
--to=wli@holomorphy.com \
--cc=jasonp@boo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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