From: Marc-Christian Petersen <mcp@linux-systeme.de>
To: linux-kernel@vger.kernel.org
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>, Adrian Bunk <bunk@fs.tum.de>
Subject: 2.4.19' drivers/block/ll_rw_blk.c
Date: Mon, 5 Aug 2002 12:23:29 +0200 [thread overview]
Message-ID: <200208051223.29329.mcp@linux-systeme.de> (raw)
Hi there,
could you please consider changing those very slow behaviour in
"drivers/block/ll_rw_blk.c"? ... Benchmarked against 2.4.18 this is horribly
slower ... Doing some heavy disk i/o, want to start another thing, system
freeze for some seconds ... Opening a xterm , Ctrl-D to leave, this takes
about 5 seconds and somewhat is doing flushing to the disk.
Maybe req_finished_io ?
Adrian, could this be the problem you've experienced?
Afaik this was changed for 2.4.19-pre7 and above.
--
Kind regards
Marc-Christian Petersen
http://sourceforge.net/projects/wolk
PGP/GnuPG Key: 1024D/408B2D54947750EC
Fingerprint: 8602 69E0 A9C2 A509 8661 2B0B 408B 2D54 9477 50EC
Key available at www.keyserver.net. Encrypted e-mail preferred.
next reply other threads:[~2002-08-05 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 10:23 Marc-Christian Petersen [this message]
2002-08-06 15:12 ` 2.4.19' drivers/block/ll_rw_blk.c Jens Axboe
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=200208051223.29329.mcp@linux-systeme.de \
--to=mcp@linux-systeme.de \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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