From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jason Papadopoulos <jasonp@boo.net>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: [PATCH] page coloring for 2.4.17 kernel
Date: Tue, 15 Jan 2002 11:22:44 +0000 [thread overview]
Message-ID: <20020115112244.C2595@redhat.com> (raw)
In-Reply-To: <3.0.6.32.20020114235555.007bfac0@boo.net>; from jasonp@boo.net on Mon, Jan 14, 2002 at 11:55:55PM -0500
Hi,
On Mon, Jan 14, 2002 at 11:55:55PM -0500, Jason Papadopoulos wrote:
> At 10:46 PM 1/14/02 +0000, you wrote:
>
> >> Hello. Please be patient with this, my first post to linux-mm.
> >> The included patch modifies the free list in the 2.4.17 kernel
> >> to support round-robin page coloring. It seems to work okay
> >> on an Alpha and speeds up a lot of number-crunching code I
> >> have lying around (lmbench reports some higher bandwidths too).
> >> The patch is a port of the 2.2.20 version that I recently posted
> >> to the linux kernelmailing list.
> >
> >Do you have numbers to show the sort of performance difference it
> >makes?
>
> It's a little difficult to tell with lmbench, since results can vary
> slightly from run to run.
That's an important aspect. Page colouring can often drastically
reduce the variance in run times for cache-intensive tasks. Average
and variance are both very much worth reporting.
Cheers,
Stephen
--
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:[~2002-01-15 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 1:46 [PATCH] page coloring for 2.4.17 kernel Jason Papadopoulos
2002-01-14 22:46 ` Stephen C. Tweedie
2002-01-15 4:55 ` Jason Papadopoulos
2002-01-15 11:22 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 6:16 Jason Papadopoulos
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=20020115112244.C2595@redhat.com \
--to=sct@redhat.com \
--cc=jasonp@boo.net \
--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.