From: Andrew Morton <akpm@osdl.org>
To: Matthias Dahl <mlkernel@mortal-soul.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sluggish system responsiveness under higher IO load
Date: Sun, 6 Aug 2006 12:37:15 -0700 [thread overview]
Message-ID: <20060806123715.b62d7b34.akpm@osdl.org> (raw)
In-Reply-To: <200608061554.42992.mlkernel@mortal-soul.de>
On Sun, 6 Aug 2006 15:54:42 +0200
Matthias Dahl <mlkernel@mortal-soul.de> wrote:
> > I'd suggest that you generate a kernel profile while the sluggishness is
> > happening.
>
> Done...
Please always do reply-to-all, especially on linux-kernel. I'm often two
days behind, sometimes five days.
> profile 1: (emerge of three huge packages which caused quite some IO)
>
> ...
>
> ffffffff803a0430 scsi_dispatch_cmd 459 0.7172
> ffffffff8026afda copy_user_generic_c 854 22.4737
> ffffffff80270e00 default_idle 49571 516.3646
> 0000000000000000 total 54590 0.0232
>
> profile 2: (emerge of recent kernel sources- huge, causes quite some IO too)
>
> ...
>
> ffffffff8020cae0 vm_normal_page 814 4.2396
> ffffffff8026ad70 copy_page 1929 8.6116
> ffffffff802075e0 unmap_vmas 2362 1.2726
> ffffffff80207d20 copy_page_range 2683 1.6938
> ffffffff80270e00 default_idle 45081 469.5938
> 0000000000000000 total 64216 0.0273
>
> I hope this helps.
Well, it rules a lot of things out. There's plenty of idle time there, so
that rules out a lot of silly things and points the finger at IO scheduler
bustage, poor page-replacement decisions, etc.
hm. Do you have any reason for thinking that it's specific to any
particular device driver or hardware setup?
How much memory does the machine have?
It'd be interesting if you could gather a `vmstat 1' trace during the
sluggish period.
next prev parent reply other threads:[~2006-08-06 19:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 10:00 sluggish system responsiveness under higher IO load Matthias Dahl
2006-08-06 10:15 ` Andrew Morton
2006-08-06 13:54 ` Matthias Dahl
2006-08-06 19:37 ` Andrew Morton [this message]
2006-08-08 15:47 ` Matthias Dahl
2006-08-07 13:48 ` Jens Axboe
2006-08-08 15:56 ` Matthias Dahl
2006-08-08 17:44 ` Matthias Dahl
2006-08-08 19:02 ` Jens Axboe
2006-08-10 12:28 ` Jens Axboe
2006-08-11 11:40 ` Matthias Dahl
2006-08-13 16:15 ` Matthias Dahl
2006-10-06 15:58 ` Paolo Ornati
2006-10-08 14:28 ` Christian
2006-10-08 17:05 ` Jens Axboe
2006-10-08 23:50 ` Jesper Juhl
2006-10-09 5:58 ` Jens Axboe
2006-10-14 14:39 ` Matthias Dahl
2006-10-14 14:57 ` Paolo Ornati
2006-10-14 18:20 ` Mike Galbraith
2006-09-03 11:15 ` Matthias Dahl
2006-09-15 18:17 ` Jens Axboe
2006-09-24 14:32 ` Matthias Dahl
2006-09-24 20:27 ` Mike Galbraith
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=20060806123715.b62d7b34.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlkernel@mortal-soul.de \
/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