From: Nick Piggin <nickpiggin@yahoo.com.au>
To: FabF <fabian.frederick@skynet.be>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Con Kolivas <kernel@kolivas.org>
Subject: Re: autoregulation needed
Date: Sat, 10 Jul 2004 22:01:13 +1000 [thread overview]
Message-ID: <40EFDA89.4020001@yahoo.com.au> (raw)
In-Reply-To: <1089453053.3646.18.camel@localhost.localdomain>
FabF wrote:
> Hi,
>
> I've been surprised these last days to read ar wasn't that interesting
> (!!!) so I did a slight bench :
>
> http://fabian.unixtech.be/kernel/autoregulate/
>
> Well, I hope we can have that pretty stuff in mainline.I'm bored
> patching it again and again.
>
> If some persons could confirm GUI is relaxed with autoregulation (well
> its my case but I could use a box from Mars or smthg :) ).
>
That is a good start.
I don't think we need to rush in changes here on the basis that
they improve a *really* thrashing workload, although obviously
that is interesting, and a definitely positive point.
I didn't see Con's newest autoswappiness patch do a great deal
for kbuild here. The inactivation thing seems to help more - it
appears to increase the rate of active list scanning, which is
consistient with the sort of behaviour I have seen. However, the
problem with increased active list scanning is that it can be
quicker to evict RSS over throwaway data which is bad.
Changes should be tested one at a time if possible, and when they
are determined to be an improvement, we should try to look into
what the "auto tuning" magic is doing right, and see if that can
be implemented in a simpler way (although it may be already as
simple as possible).
next prev parent reply other threads:[~2004-07-10 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 9:50 autoregulation needed FabF
2004-07-10 12:01 ` Nick Piggin [this message]
2004-07-10 12:30 ` [PATCH] Autotune inactivation Con Kolivas
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=40EFDA89.4020001@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=fabian.frederick@skynet.be \
--cc=kernel@kolivas.org \
--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