From: Stephen Tweedie <sct@redhat.com>
To: Fireball Freddy <fireballfreddy@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: Comparing buffer cache algorithms on 2.2.17. Suggestions?
Date: Mon, 19 Feb 2001 19:10:11 +0000 [thread overview]
Message-ID: <20010219191011.A1190@redhat.com> (raw)
In-Reply-To: <20010217221540.23972.qmail@web2104.mail.yahoo.com>
In-Reply-To: <20010217221540.23972.qmail@web2104.mail.yahoo.com>; from fireballfreddy@yahoo.com on Sat, Feb 17, 2001 at 02:15:40PM -0800
Hi,
On Sat, Feb 17, 2001 at 02:15:40PM -0800, Fireball Freddy wrote:
>
> o Eliminate BUF_CLEAN, BUF_DIRTY, and BUF_LOCKED
> lists in favor of a single BUF_LRU list. This because
> I don't see the point of maintaining three lists...
> the only time I need to find all the dirty blocks is
> on a sync of some sort. I don't mind if the sync
> takes a while longer if the normal operating condition
> is faster.
What if you have a gig of buffer cache in the system? You still need
to maintain the single LRU, so you're not going to be saving that much
on the main codepaths, and walking a gig of unnecessary buffer_heads
every kupdate() flush is not going to be cheap.
> It looks like the ext2 fs is going to complicate
> this somewhat, as it sets blocks dirty and/or writes
> them itself sometimes. Not sure how I'm going to get
> around this... will probably ignore it for now.
Yep, this behaviour on the superblock and group descriptors has hurt
people in the past.
Cheers,
Stephen
prev parent reply other threads:[~2001-02-20 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 22:15 Comparing buffer cache algorithms on 2.2.17. Suggestions? Fireball Freddy
2001-02-19 19:10 ` Stephen Tweedie [this message]
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=20010219191011.A1190@redhat.com \
--to=sct@redhat.com \
--cc=fireballfreddy@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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.