From: john <john@zlilo.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: john <john@zlilo.com>, linux-kernel@vger.kernel.org
Subject: Re: kupdated using all CPU
Date: Mon, 18 Feb 2002 14:19:20 -0800 [thread overview]
Message-ID: <20020218141920.D2586@doom.sfo.covalent.net> (raw)
In-Reply-To: <20020218134041.A2586@doom.sfo.covalent.net> <3C717C72.72A994D3@zip.com.au>
In-Reply-To: <3C717C72.72A994D3@zip.com.au>; from akpm@zip.com.au on Mon, Feb 18, 2002 at 02:13:06PM -0800
[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
next prev parent reply other threads:[~2002-02-18 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 21:40 john
2002-02-18 22:13 ` Andrew Morton
2002-02-18 22:19 ` john [this message]
2002-02-18 22:47 ` Andrew Morton
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=20020218141920.D2586@doom.sfo.covalent.net \
--to=john@zlilo.com \
--cc=akpm@zip.com.au \
--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
all inboxes | Powered by JetHome®