mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc5-mm3
Date: Thu, 22 Dec 2005 15:16:10 +1100	[thread overview]
Message-ID: <cone.1135224970.635407.3942.501@kolivas.org> (raw)
In-Reply-To: <9a8748490512211514g62bec66dqfb00b4dc1aeb7628@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

Jesper Juhl writes:

> On 12/15/05, Andrew Morton <akpm@osdl.org> wrote:
>>
> <!-- snip -->
>>
>> -mm-implement-swap-prefetching.patch
>> -mm-implement-swap-prefetching-default-y.patch
>> -mm-implement-swap-prefetching-tweaks.patch
>> -mm-implement-swap-prefetching-tweaks-2.patch
>> -mm-swap-prefetch-magnify.patch
>>
>>  Dropped swap prefetching, sorry.  I wasn't able to notice much benefit from
>>  it in my testing, and the number of mm/ patches in getting crazy, so we don't
>>  have capacity for speculative things at present.
>>
> <!-- snip -->
> 
> This is a bit sad.
> On my system (1.4GHz Athlon w/512MB RAM, 768MB swap) this did have an effect.
> One situation in particular where it helped (and which is a common
> case for me) was when I had OpenOffice2 + Eclipse (with CDT) + xchat +
> nedit + Firefox + a few konsole windows open (running KDE 3.5 btw and
> all apps usually have a lot of content loaded), minimized all the apps
> and then started an allyesconfig build in one window - the
> allyesconfig build would drag the machine to its knees and eat up more
> or less all RAM + swap, so I usually left it alone for a while to
> finish and when I then came back later and reactivated the apps I had
> minimized they came back pretty fast. Without the swap prefetch
> patches things come back somewhat slower - it's not an earth
> shattering difference, but it's definately noticable.

Apart from the feedback I've gotten directly from users of the -ck patchset 
incorporating this, Andrew and lkml has had very few reports about it until 
he decided to drop it. I'm still maintaining the code in -ck indefinitely 
for the moment. Here's hoping he picks it up again in the future.

Cheers,
Con


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-22  4:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15  7:40 2.6.15-rc5-mm3 Andrew Morton
2005-12-15  9:48 ` 2.6.15-rc5-mm3 Andi Kleen
2005-12-15 15:36   ` 2.6.15-rc5-mm3 Andi Kleen
2005-12-15 14:30 ` 2.6.15-rc5-mm3 Alexander E. Patrakov
2005-12-16 12:50 ` 2.6.15-rc5-mm3 Lenar Lõhmus
2005-12-16 23:17 ` 2.6.15-rc5-mm3 Greg KH
2005-12-17  0:15   ` 2.6.15-rc5-mm3 J.A. Magallon
2005-12-17  1:42     ` 2.6.15-rc5-mm3 Greg KH
2005-12-20 21:03   ` [PATCH] pci device sysdata may be null check in pcibus_to_node Andy Whitcroft
2005-12-20 23:16     ` Andrew Morton
2005-12-22 21:06       ` [PATCH] pci device ensure sysdata initialised Andy Whitcroft
2005-12-22 23:18         ` Greg KH
2005-12-22 23:43           ` Andy Whitcroft
2005-12-22 23:51             ` Greg KH
2005-12-22 23:56               ` Andy Whitcroft
2005-12-18  8:16 ` 2.6.15-rc5-mm3 Grant Coady
2005-12-18 11:31   ` 2.6.15-rc5-mm3 Rafael J. Wysocki
2005-12-18 19:54     ` 2.6.15-rc5-mm3 Grant Coady
2005-12-22 17:48     ` 2.6.15-rc5-mm3 Greg KH
2005-12-23  1:05       ` 2.6.15-rc5-mm3 David Brownell
2005-12-21 23:14 ` 2.6.15-rc5-mm3 Jesper Juhl
2005-12-22  4:16   ` Con Kolivas [this message]
2005-12-22 18:13   ` 2.6.15-rc5-mm3 Mattia Dongili
2005-12-29 23:46 ` 2.6.15-rc5-mm3 [BUG] smp_processor_id() in preemptible code Peter Williams

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=cone.1135224970.635407.3942.501@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®