From: Jens Axboe <axboe@suse.de>
To: Simone Piunno <simone.piunno@wseurope.com>
Cc: Baruch Even <baruch@ev-en.org>,
Fabio Coatti <fabio.coatti@wseurope.com>,
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 16:16:44 +0100 [thread overview]
Message-ID: <20050311151644.GJ28188@suse.de> (raw)
In-Reply-To: <200503111514.34949.simone.piunno@wseurope.com>
On Fri, Mar 11 2005, Simone Piunno wrote:
> Alle 14:29, venerdì 11 marzo 2005, Baruch Even ha scritto:
>
> > echo t > /proc/sysrq-trigger
>
> Before killing bonnie:
I'm guessing your problem is that bonnie dirtied tons of data before you
killed it, so it has to flush it out. If you run out of request entries,
you will get to sleep uninterruptibly on those while the data is
flushing. I don't see anything unexpected here, it is normal behaviour.
> bonnie++ D ffff81010383f820 0 2042 2016
> (NOTLB)
> ffff8100f51d7248 0000000000000082 000000010000007d 000000000003bd42
> ffff8101ffeee1f0 ffff8101ff538a60 ffff8101ff538cd8 0000000000000292
> 0000000000000292 0000000000000282
> Call Trace:<ffffffff804a0b11>{io_schedule+49}
> <ffffffff80365a8e>{get_request_wait+174}
> <ffffffff801459d0>{autoremove_wake_function+0}
> <ffffffff801459d0>{autoremove_wake_function+0}
> <ffffffff8036697c>{__make_request+812}
This is what is happening here, after you kill it.
--
Jens Axboe
next prev parent reply other threads:[~2005-03-11 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 11:08 bonnie++ uninterruptible under heavy I/O load 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 [this message]
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
2005-03-11 16:24 ` Simone Piunno
-- strict thread matches above, loose matches on Subject: below --
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=20050311151644.GJ28188@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 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.