From: Jens Axboe <axboe@suse.de>
To: Dieter Nützel <Dieter.Nuetzel@hamburg.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andrea Arcangeli <andrea@suse.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.1-pre11 / ll_rw_b watermark metric?
Date: Mon, 29 Jan 2001 04:46:40 +0100 [thread overview]
Message-ID: <20010129044640.B15679@suse.de> (raw)
In-Reply-To: <01012904435200.00697@SunWave1>
In-Reply-To: <01012904435200.00697@SunWave1>; from Dieter.Nuetzel@hamburg.de on Mon, Jan 29, 2001 at 04:43:52AM +0100
On Mon, Jan 29 2001, Dieter Nützel wrote:
> I have pre11 running with Andrea's suggested fix.
>
> high_queued_sectors = total_ram / 3;
> low_queued_sectors = high_queued_sectors / 2;
> if (low_queued_sectors < 0)
> low_queued_sectors = total_ram / 2;
>
> /*
> * for big RAM machines (>= 384MB), use more for I/O
> */
> /*
> if (total_ram >= MB(384)) {
> high_queued_sectors = (total_ram * 4) / 5;
> low_queued_sectors = high_queued_sectors - MB(128);
> }
> */
>
> Shouldn't it be clean for a 2.4.1 release?
With enough swap the numbers I saw were not conclusive. I promised
to test which I haven't gotten done yet, I will do this tomorrow
and make sure we have the right ratios. However, I don't think
the pre11 numbers are much off - do you have any results?
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 3:43 Linux-2.4.1-pre11 / ll_rw_b watermark metric? Dieter Nützel
2001-01-29 3:46 ` Jens Axboe [this message]
2001-01-29 4:01 ` Dieter Nützel
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 11:56 Petr Vandrovec
2001-01-29 15:12 ` 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=20010129044640.B15679@suse.de \
--to=axboe@suse.de \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.