mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Simone Piunno <simone.piunno@wseurope.com>
Cc: Fabio Coatti <fabio.coatti@wseurope.com>,
	Baruch Even <baruch@ev-en.org>,
	Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	linux-kernel@vger.kernel.org
Subject: Re: bonnie++ uninterruptible under heavy I/O load
Date: Fri, 11 Mar 2005 17:00:48 +0100	[thread overview]
Message-ID: <20050311160048.GM28188@suse.de> (raw)
In-Reply-To: <200503111658.04499.simone.piunno@wseurope.com>

On Fri, Mar 11 2005, Simone Piunno wrote:
> Alle 16:54, venerdì 11 marzo 2005, Jens Axboe ha scritto:
> 
> > I'd guess that your problem is queueing, if you have a ton of pending
> > requests in the hardware it will take forever to get a new request
> > through. There's nothing the io scheduler can do to help you there,
> > really. The /proc/driver/cciss/cciss0 you originall posted, was that
> > from before or after running bonnie++? I have no latency experience with
> > cciss, at least IDE/SATA/SCSI should work alright.
> 
> It was after running bonnie++.

Are you sure? It lists only 190 commands run since it initialized,
that's basically nothing. 6 was the highest depth, should not be enough
to cause serious latency issues unless it was constantly at 6.

-- 
Jens Axboe


  reply	other threads:[~2005-03-11 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 11:08 Simone Piunno
2005-03-11 11:35 ` Denis Vlasenko
2005-03-11 13:20   ` Fabio Coatti
2005-03-11 13:29     ` Baruch Even
2005-03-11 14:14       ` Simone Piunno
2005-03-11 15:16         ` Jens Axboe
2005-03-11 15:50           ` Fabio Coatti
2005-03-11 15:54             ` Jens Axboe
2005-03-11 15:58               ` Simone Piunno
2005-03-11 16:00                 ` Jens Axboe [this message]
2005-03-11 16:24                   ` Simone Piunno
2005-03-11 14:24 Christian Guggenberger

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=20050311160048.GM28188@suse.de \
    --to=axboe@suse.de \
    --cc=baruch@ev-en.org \
    --cc=fabio.coatti@wseurope.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simone.piunno@wseurope.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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®