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] page coloring for 2.5.59 kernel, version 1
Date: Mon, 27 Jan 2003 19:57:36 -0800 [thread overview]
Message-ID: <20030128035736.GF780@holomorphy.com> (raw)
In-Reply-To: <3.0.6.32.20030127224726.00806c20@boo.net>
On Mon, Jan 27, 2003 at 10:47:26PM -0500, Jason Papadopoulos wrote:
> This is yet another holding action, a port of my page coloring patch
> to the 2.5 kernel. This is a minimal port (x86 only) intended to get
> some testing done; once again the algorithm used is the same as in
> previous patches. There are several cleanups and removed 2.4-isms that
> make the code somewhat more compact, though.
> I'll be experimenting with other coloring schemes later this week.
> www.boo.net/~jasonp/page_color-2.5.59-20030127.patch
> Feedback of any sort welcome.
set_num_colors() needs to go downstairs under arch/ Some of the
current->pid checks look a bit odd esp. for GFP_ATOMIC and/or
in_interrupt() cases. I'm not sure why this is a config option; it
should be mandatory. I also wonder about the interaction of this with
the per-cpu lists. This may really want to be something like a matrix
with (cpu, color) indices to find the right list; trouble is, there's a
high potential for many pages to be trapped there. mapnr's (page -
zone->zone_mem_map etc.) are being used for pfn's; this may raise
issues if zones' required alignments aren't num_colors*PAGE_SIZE or
larger. proc_misc.c can be used instead of page_color_init(). ->free_list
can be removed. get_rand() needs locking, per-zone state. Useful stuff.
--wli
WARNING: multiple messages have this Message-ID (diff)
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] page coloring for 2.5.59 kernel, version 1
Date: Mon, 27 Jan 2003 19:57:36 -0800 [thread overview]
Message-ID: <20030128035736.GF780@holomorphy.com> (raw)
In-Reply-To: <3.0.6.32.20030127224726.00806c20@boo.net>
On Mon, Jan 27, 2003 at 10:47:26PM -0500, Jason Papadopoulos wrote:
> This is yet another holding action, a port of my page coloring patch
> to the 2.5 kernel. This is a minimal port (x86 only) intended to get
> some testing done; once again the algorithm used is the same as in
> previous patches. There are several cleanups and removed 2.4-isms that
> make the code somewhat more compact, though.
> I'll be experimenting with other coloring schemes later this week.
> www.boo.net/~jasonp/page_color-2.5.59-20030127.patch
> Feedback of any sort welcome.
set_num_colors() needs to go downstairs under arch/ Some of the
current->pid checks look a bit odd esp. for GFP_ATOMIC and/or
in_interrupt() cases. I'm not sure why this is a config option; it
should be mandatory. I also wonder about the interaction of this with
the per-cpu lists. This may really want to be something like a matrix
with (cpu, color) indices to find the right list; trouble is, there's a
high potential for many pages to be trapped there. mapnr's (page -
zone->zone_mem_map etc.) are being used for pfn's; this may raise
issues if zones' required alignments aren't num_colors*PAGE_SIZE or
larger. proc_misc.c can be used instead of page_color_init(). ->free_list
can be removed. get_rand() needs locking, per-zone state. Useful stuff.
--wli
--
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-28 3:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 3:47 [PATCH] page coloring for 2.5.59 kernel, version 1 Jason Papadopoulos
2003-01-28 3:47 ` Jason Papadopoulos
2003-01-28 3:57 ` William Lee Irwin III [this message]
2003-01-28 3:57 ` William Lee Irwin III
2003-01-28 4:11 ` William Lee Irwin III
2003-01-28 4:11 ` William Lee Irwin III
2003-01-28 6:58 ` Martin J. Bligh
2003-01-28 6:58 ` Martin J. Bligh
2003-01-28 7:13 ` William Lee Irwin III
2003-01-28 7:13 ` William Lee Irwin III
2003-01-28 16:06 ` Martin J. Bligh
2003-01-28 16:06 ` Martin J. Bligh
2003-01-28 16:41 ` Falk Hueffner
2003-01-28 16:41 ` Falk Hueffner
[not found] <3.0.6.32.20030127224726.00806c20@boo.net.suse.lists.linux.kernel>
[not found] ` <884740000.1043737132@titus.suse.lists.linux.kernel>
[not found] ` <20030128071313.GH780@holomorphy.com.suse.lists.linux.kernel>
[not found] ` <1466000000.1043770007@titus.suse.lists.linux.kernel>
2003-01-28 16:37 ` Andi Kleen
2003-01-28 16:37 ` Andi Kleen
2003-01-28 16:49 ` Martin J. Bligh
2003-01-28 16:49 ` Martin J. Bligh
2003-01-28 17:06 ` Bill Davidsen
2003-01-28 17:06 ` Bill Davidsen
2003-01-28 17:22 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2003-01-28 17:49 jasonp
2003-01-28 17:49 ` jasonp
2003-01-28 18:01 jasonp
2003-01-28 18:01 ` jasonp
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=20030128035736.GF780@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 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.