From: Mike Fedyk <mfedyk@matchmail.com>
To: kernel-list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.11.p4 and dd
Date: Tue, 9 Oct 2001 13:55:28 -0700 [thread overview]
Message-ID: <20011009135528.A20914@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110081343280.1775-100000@boris.prodako.se> <3BC2A130.CFEBBE2D@isg.de>
In-Reply-To: <3BC2A130.CFEBBE2D@isg.de>
On Tue, Oct 09, 2001 at 09:03:12AM +0200, Constantin Loizides wrote:
> Hi!
>
> > > 2.4.3 uses a large amount of buffer, 2.4.11p4 only chache.
> >
> > Block devices are handled by the page cache in 2.4.10 and up.
> >
>
> Eh, did I miss something?
Yes.
>Thought, that meta data are still
> cached in buffer cache?
FSes still use the buffer cache, but the block devices now use page cache.
>Did it change from 2.4.9 to 2.4.10?
Yes, in 2.4.10pre11
> What about the ac kernels?
>
Block devices use Buffer Cache. Alan has stated that he doesn't plan to
merge this change any time soon, if at all.
> Constantin
Mike
next prev parent reply other threads:[~2001-10-09 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-07 18:35 2.4.11.p4 and dd Klaus Dittrich
2001-10-08 11:45 ` Tobias Ringstrom
2001-10-09 7:03 ` Constantin Loizides
2001-10-09 20:55 ` Mike Fedyk [this message]
2001-10-08 12:04 ` Stephan von Krawczynski
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=20011009135528.A20914@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox