From: Andrea Arcangeli <andrea@suse.de>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org, Con Kolivas <conman@kolivas.net>
Subject: Re: 2.[45] fixes for design locking bug in wait_on_page/wait_on_buffer/get_request_wait
Date: Sat, 16 Nov 2002 19:46:22 +0100 [thread overview]
Message-ID: <20021116184622.GJ31697@dualathlon.random> (raw)
In-Reply-To: <200211161841.59889.m.c.p@wolk-project.de>
On Sat, Nov 16, 2002 at 06:43:36PM +0100, Marc-Christian Petersen wrote:
> On Saturday 16 November 2002 18:32, Andrea Arcangeli wrote:
>
> Hi Andrea,
>
> > you may want to try with this setting that helps with very slow devices:
> > echo 2 500 0 0 500 3000 3 1 0 > /proc/sys/vm/bdflush
> >
> > or also with my current default tuned for high performance:
> > echo 50 500 0 0 500 3000 60 20 > /proc/sys/vm/bdflush
> I've tested both without any changes, "pausings" are still there.
>
> > you may have too many dirty buffers around and you end running at disk
> > speed at every memory allocation, the first setting will decrease the
> > amount of dirty buffers dramatically, if you still have significant
> > slowdown with the first setting above, it's most probably only the usual
> > elevator issue.
> Seems so.
>
> So I have to use 2.4.18 until there is a real proper fix for that.
just to make a quick test, can you try an hack like this combined with a
setting of elvtune -r 128 -w 256 on top of 2.4.20rc1?
--- x/drivers/block/ll_rw_blk.c.~1~ Sat Nov 2 19:45:33 2002
+++ x/drivers/block/ll_rw_blk.c Sat Nov 16 19:44:20 2002
@@ -432,7 +432,7 @@ static void blk_init_free_list(request_q
si_meminfo(&si);
megs = si.totalram >> (20 - PAGE_SHIFT);
- nr_requests = 128;
+ nr_requests = 16;
if (megs < 32)
nr_requests /= 2;
blk_grow_request_list(q, nr_requests);
Andrea
next prev parent reply other threads:[~2002-11-16 18:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 16:24 2.[45] fixes for design locking bug in wait_on_page/wait_on_buffer/get_request_wait Marc-Christian Petersen
2002-11-16 16:59 ` Andrea Arcangeli
2002-11-16 17:23 ` Marc-Christian Petersen
2002-11-16 17:32 ` Andrea Arcangeli
2002-11-16 17:43 ` Marc-Christian Petersen
2002-11-16 18:46 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-16 18:58 Marc-Christian Petersen
2002-11-16 21:55 ` Marc-Christian Petersen
2002-11-17 17:37 ` Marc-Christian Petersen
2002-11-17 19:19 ` Folkert van Heusden
2002-11-12 3:57 Andrea Arcangeli
2002-11-12 8:50 ` Andrew Morton
2002-11-12 18:15 ` Andrea Arcangeli
2002-11-12 19:46 ` Andrew Morton
2002-11-13 0:33 ` Andrea Arcangeli
2002-11-13 1:01 ` Andrew Morton
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=20021116184622.GJ31697@dualathlon.random \
--to=andrea@suse.de \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.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