From: Martin Steigerwald <Martin@lichtvoll.de>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Subranshu Patel <spatel.ml@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Large buffer cache in EXT4
Date: Mon, 18 Feb 2013 14:16:24 +0100 [thread overview]
Message-ID: <201302181416.24599.Martin@lichtvoll.de> (raw)
In-Reply-To: <20130218043517.GB10361@thunk.org>
Am Montag, 18. Februar 2013 schrieb Theodore Ts'o:
> On Sun, Feb 17, 2013 at 11:25:39AM +0100, Martin Steigerwald wrote:
> > What I never really understand was what is the clear distinction
> > between dirty pages and disk block buffers. Why isn´t anything that is
> > about to be written to disk in one cache?
>
> The buffer cache is indexed by physical block number, and each buffer
> in the buffer cache is the size of the block size used for I/O to the
> device.
>
> The page cache is indexed by <inode, page frame number>, and each page
> is the size of a VM page (i.e.4k for x86 systems, 16k for Power
> systems, etc.)
>
> Certain file systems, including ext3, ext4, and ocfs2, use the jbd or
> jbd2 layer to handle their physical block journalling, and this layer
> fundamentally uses the buffer cache, since it is concerned with
> controlling when specific file system blocks are allowed to ben
> written back to the hard drive.
Thank you for the explanation, Ted.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-02-18 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 4:04 Large buffer cache in EXT4 Subranshu Patel
2013-02-17 6:28 ` Andreas Dilger
2013-02-17 10:19 ` Martin Steigerwald
2013-02-18 15:22 ` Eric Sandeen
2013-02-17 10:25 ` Martin Steigerwald
2013-02-18 4:35 ` Theodore Ts'o
2013-02-18 13:16 ` Martin Steigerwald [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=201302181416.24599.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-ext4@vger.kernel.org \
--cc=spatel.ml@gmail.com \
--cc=tytso@mit.edu \
/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