From: Jens Axboe <axboe@suse.de>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Dieter Nuetzel <Dieter.Nuetzel@hamburg.de>,
Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Linux-2.4.1-pre11 / ll_rw_b watermark metric?
Date: Mon, 29 Jan 2001 16:12:51 +0100 [thread overview]
Message-ID: <20010129161251.F19381@suse.de> (raw)
In-Reply-To: <13F3075C2004@vcnet.vc.cvut.cz>
In-Reply-To: <13F3075C2004@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Mon, Jan 29, 2001 at 11:56:13AM +0000
On Mon, Jan 29 2001, Petr Vandrovec wrote:
> On 29 Jan 01 at 4:43, 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;
> >
>
> I have one question: How it can happen that low_queued_sectors
> is less than zero with this changed logic? (And if it get triggered,
> low_queued_sectors will be greater than high_queued_sectors - which
> is not what we want...)
This wasn't my change, but you're right it's wrong.
> But it is certainly better than 2.4.0-pre8 approach, as
> with 200MB of memory (exactly 192MB left unused) you can end up with
> low_queued_sectors == 0... And it does not give you optimal behavior.
Same here, definitely not right either. Dunno how I missed that.
--
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 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 11:56 Linux-2.4.1-pre11 / ll_rw_b watermark metric? Petr Vandrovec
2001-01-29 15:12 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 3:43 Dieter Nützel
2001-01-29 3:46 ` Jens Axboe
2001-01-29 4:01 ` Dieter Nützel
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=20010129161251.F19381@suse.de \
--to=axboe@suse.de \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=VANDROVE@vc.cvut.cz \
--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.