From: Peter Williams <pwil3058@bigpond.net.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Con Kolivas <kernel@kolivas.org>,
linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: [PATCH] mm: Implement swap prefetching tweaks
Date: Sat, 11 Mar 2006 10:11:24 +1100 [thread overview]
Message-ID: <4412079C.5000200@bigpond.net.au> (raw)
In-Reply-To: <20060310143545.74a9a92a.akpm@osdl.org>
Andrew Morton wrote:
> Con Kolivas <kernel@kolivas.org> wrote:
>
>>+ /*
>>+ * get_page_state is super expensive so we only perform it every
>>+ * SWAP_CLUSTER_MAX prefetched_pages.
>
>
> nr_running() is similarly expensive btw.
>
>
>> * We also test if we're the only
>>+ * task running anywhere. We want to have as little impact on all
>>+ * resources (cpu, disk, bus etc). As this iterates over every cpu
>>+ * we measure this infrequently.
>>+ */
>>+ if (!(sp_stat.prefetched_pages % SWAP_CLUSTER_MAX)) {
>>+ unsigned long cpuload = nr_running();
>>+
>>+ if (cpuload > 1)
>>+ goto out;
>
>
> Sorry, this is just wrong. If swap prefetch is useful then it's also
> useful if some task happens to be sitting over in the corner calculating
> pi.
On SMP systems, something based on the run queues' raw_weighted_load
fields (comes with smpnice patch) might be more useful than nr_running()
as it contains information about the priority of the running tasks.
Perhaps (raw_weighted_load() > SCHED_LOAD_SCALE) or some variation,
where raw_weighted_load() is the sum of that field for all CPUs) would
suffice. It would mean "there's more than the equivalent of one nice==0
task running" and shouldn't be any more expensive than nr_running().
Dividing SCHED_LOAD_SCALE by some number would be an obvious variation
to try as would taking into account this process's contribution to the
weighted load.
Also if this was useful there's no real reason that raw_weighted_load
couldn't be made available on non SMP systems as well as SMP ones.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-03-10 23:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 9:54 [PATCH] mm: Implement swap prefetching tweaks Con Kolivas
2006-03-10 22:35 ` Andrew Morton
2006-03-10 23:11 ` Peter Williams [this message]
2006-03-11 4:18 ` Con Kolivas
2006-03-11 4:28 ` Peter Williams
2006-03-11 4:34 ` Con Kolivas
2006-03-11 5:34 ` Peter Williams
2006-03-11 5:04 ` [ck] " Radoslaw Szkodzinski
2006-03-11 5:21 ` Con Kolivas
2006-03-11 5:46 ` Peter Williams
2006-03-11 3:50 ` Con Kolivas
2006-03-11 5:33 ` Mike Galbraith
2006-03-11 5:50 ` Con Kolivas
2006-03-11 5:58 ` Con Kolivas
2006-03-11 6:11 ` Mike Galbraith
2006-03-11 6:00 ` Mike Galbraith
2006-03-11 6:05 ` Mike Galbraith
2006-03-11 7:20 ` Con Kolivas
2006-03-11 7:44 ` Mike Galbraith
2006-03-11 8:16 ` Nick Piggin
2006-03-11 8:22 ` Mike Galbraith
2006-03-11 7:24 ` Con Kolivas
2006-03-11 7:51 ` Mike Galbraith
2006-03-11 8:15 ` Con Kolivas
2006-03-12 4:54 ` Lee Revell
2006-03-12 5:27 ` Mike Galbraith
2006-03-12 8:36 ` Con Kolivas
2006-03-14 6:40 ` Mike Galbraith
2006-03-14 6:50 ` Lee Revell
2006-03-14 7:06 ` Mike Galbraith
2006-03-14 8:44 ` Mike Galbraith
2006-03-14 8:05 ` [ck] " Jens Axboe
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=4412079C.5000200@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--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 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.