mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.10-rc1 and prev] System unuseable while writing to disk
Date: Wed, 10 Nov 2004 14:46:33 -0500	[thread overview]
Message-ID: <41927019.9050508@tmr.com> (raw)
In-Reply-To: <418FE968.4030300@gmx.de>

Prakash K. Cheemplavam wrote:
> Hi,
> 
> I have a problem which doesn't seem to be connected to the i/o 
> schedulers, because all I tested (cfq, deadline, noop) show the same:
> 
> While writing (when the kernel actually commits to hd) my system gets 
> very unresponsive esp when another app I want to use wants to write 
> (read?) from hd, as well. This is *not* a UDMA problem (at least no 
> apparent...)! More specific:
> 
> I wrote this primitive code for writing sequentially:

May I suggest running "vmstat 1" while this is happening? Looking at the 
waitio time vs. transfer rates might reveal something. If it all looks 
the same post a small section, if it starts off looking like one thing 
and then changes as buffers fill, data from start to steady state might 
assist someone in helping.

I can't say that I see any such thing with ext[23], so it may be a 
reiser issue and someone else will have to help. Did you look at the 
logs to see that there are no useful warnings there?

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  reply	other threads:[~2004-11-10 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 21:47 Prakash K. Cheemplavam
2004-11-10 19:46 ` Bill Davidsen [this message]
2004-11-11  7:07   ` Prakash K. Cheemplavam
2004-11-11  7:33     ` Nick Piggin
2004-11-11  7:43       ` Prakash K. Cheemplavam
2004-11-20 14:13       ` Prakash K. Cheemplavam

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=41927019.9050508@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakashkc@gmx.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

Powered by JetHome