From: Mike Galbraith <efault@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: [PATCH] mm: Implement swap prefetching tweaks
Date: Sat, 11 Mar 2006 06:33:59 +0100 [thread overview]
Message-ID: <1142055239.7819.47.camel@homer> (raw)
In-Reply-To: <200603111450.39305.kernel@kolivas.org>
On Sat, 2006-03-11 at 14:50 +1100, Con Kolivas wrote:
> On Saturday 11 March 2006 09:35, 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.
>
> Yes which is why I do it just as infrequently as get_page_state.
> >
> > > * 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.
> >
> > What's the actual problem here? Someone's 3d game went blippy? Why? How
> > much? Are we missing a cond_resched()?
>
> No, it's pretty easy to reproduce, kprefetchd sits there in uninterruptible
> sleep with one cpu on SMP pegged at 100% iowait due to it. This tends to have
> noticeable effects everywhere on HT or SMP. On UP the yielding helped it but
> even then it still causes blips. How much? Well to be honest it's noticeable
> a shipload. Running a game, any game, that uses 100% (and most fancy games
> do) causes stuttering on audio, pauses and so on. This is evident on linux
> native games, games under emulators or qemu and so on. That iowait really
> hurts, and tweaking just priority doesn't help it in any way.
That doesn't really make sense to me. If a task can trigger audio
dropout and stalls by sleeping, we have a serious problem. In your
SMP/HT case, I'd start crawling over the load balancing code. I can't
see how trivial CPU with non-saturated IO can cause dropout in the UP
case either. Am I missing something?
-Mike
next prev parent reply other threads:[~2006-03-11 5:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 9:54 Con Kolivas
2006-03-10 22:35 ` Andrew Morton
2006-03-10 23:11 ` Peter Williams
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 [this message]
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=1142055239.7819.47.camel@homer \
--to=efault@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome