public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, ck list <ck@vds.kolivas.org>
Subject: Re: [PATCH] mm - swap prefetch magnify
Date: Sun, 23 Oct 2005 01:21:30 +1000	[thread overview]
Message-ID: <200510230121.31048.kernel@kolivas.org> (raw)
In-Reply-To: <4d8e3fd30510220241i6c370dd1x512561cb6a1bc250@mail.gmail.com>

On Sat, 22 Oct 2005 19:41, Paolo Ciarrocchi wrote:
> On 10/22/05, Con Kolivas <kernel@kolivas.org> wrote:
> > On Sat, 22 Oct 2005 11:20, Con Kolivas wrote:
> > > Testing has confirmed much larger prefetch values work well.
> >
> > Bah.. Sorry take this one instead. Just make sure that no matter how
> > little ram we have prefetch is enabled.
>
> Con,
> would you be so kind to post more information about the test you've done ?

My concern was to not cause a detriment to performance in any noticeable way. 
The prefetch sizes were tested on a number of machines with different speed 
hard drive / ram size combinations to ensure none of the default values ever 
caused any significant I/O wait, or that heavy memory requiring compiles took 
any longer to complete as these constantly need new ram allocations and I 
wanted to ensure that prefetching into ram didn't slow down those 
allocations. Furthermore, the time taken to actually prefetch the application 
is now more than 5 times faster because of the larger default prefetch 
values.

Cheers,
Con

      reply	other threads:[~2005-10-22 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22  1:20 [PATCH] mm - swap prefetch magnify Con Kolivas
2005-10-22  1:47 ` Con Kolivas
2005-10-22  9:41   ` Paolo Ciarrocchi
2005-10-22 15:21     ` Con Kolivas [this message]

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=200510230121.31048.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.ciarrocchi@gmail.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