From: Charles-Edouard Ruault <ce@ruault.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Francois Romieu <romieu@fr.zoreil.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.21 , large disk write => system crawls
Date: Fri, 04 Jul 2003 01:06:02 +0200 [thread overview]
Message-ID: <3F04B6DA.2040300@ruault.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307031848420.7338-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>>>>when i do a large disk write operation ( copy a big file for example ),
>>>>the whole system becomes very busy ( system goes into 99% cpu
>>>>
>>>>
>
>it's not write-specific. you can see below that you're somehow
>managing to trigger roughly two interrupts per *either* bi or bo.
>for a normal IDE setup, you should see one interrupt per 16-64K
>under average use. it's almost like your sys somehow thinks
>that it can only transfer 1 sector per interrupt!
>
>
hmmm interesting i had not noticed that !
>
>
>>everytime i experience a slowdown, there's a 'big' number in the io (bo)
>>column.
>>
>>
>
>no, it's basically in=2*(bi+bo), as if your system somehow believes
>it can only do a single sector per interrupt (PIO and -m1 perhaps?)
>it should be more like 32K per interrupt.
>
>
>
>>Jun 27 22:52:31 charlus kernel: Found and enabled local APIC!
>>
>>
>
>have you tried without that?
>
>.
>
>
>
nope. I'll do that for sure. I've already had problems with APIC on
other systems ...
Thanks for the hint. I'll keep you posted if it works.
--
Charles-Edouard Ruault
PGP Key ID E10C24DC
next prev parent reply other threads:[~2003-07-03 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 21:34 kernel 2.4.21 , large disk write => system crawls Charles-Edouard Ruault
2003-07-03 22:02 ` Francois Romieu
2003-07-03 22:30 ` Charles-Edouard Ruault
2003-07-03 22:56 ` Mark Hahn
2003-07-03 23:06 ` Charles-Edouard Ruault [this message]
2003-07-06 17:20 ` Jakob Oestergaard
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=3F04B6DA.2040300@ruault.com \
--to=ce@ruault.com \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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.