From: Andrew Morton <akpm@zip.com.au>
To: john <john@zlilo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kupdated using all CPU
Date: Mon, 18 Feb 2002 14:47:38 -0800 [thread overview]
Message-ID: <3C71848A.3DA9BC42@zip.com.au> (raw)
In-Reply-To: <20020218134041.A2586@doom.sfo.covalent.net> <3C717C72.72A994D3@zip.com.au>, <3C717C72.72A994D3@zip.com.au>; from akpm@zip.com.au on Mon, Feb 18, 2002 at 02:13:06PM -0800 <20020218141920.D2586@doom.sfo.covalent.net>
john wrote:
>
> [Mon, Feb 18, 2002 at 02:13:06PM -0800] akpm@zip.com.au wrote:
> + john wrote:
> + >
> + > hi,
> + > ive searched all over and found many references to this problem, but
> + > never found an actual solution. the problem is that during heavy
> + > disk I/O, kupdated will periodically take up ALL the cpu.
> +
> + I've seen a couple of reports of this, nothing to indicate that it's
> + a common problem?
> +
> + In the other reports, it was related to extremely low disk throughput.
> + What does `hdparm -t /dev/hda' say?
>
> root@doom:~# hdparm -t /dev/hda
>
> /dev/hda:
> Timing buffered disk reads: 64 MB in 25.60 seconds = 2.50 MB/sec
ugh. OK, I'll see if I cen reproduce this - there's no reason
why disk suckiness should cause high CPU load. But you need to
pay some attention to your IDE settings in kernel config, and
possibly tuning.
-
next prev parent reply other threads:[~2002-02-18 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 21:40 kupdated using all CPU john
2002-02-18 22:13 ` Andrew Morton
2002-02-18 22:19 ` john
2002-02-18 22:47 ` Andrew Morton [this message]
2002-02-19 4:53 ` Eric W. Biederman
2002-02-19 17:42 ` john
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=3C71848A.3DA9BC42@zip.com.au \
--to=akpm@zip.com.au \
--cc=john@zlilo.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 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.