public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Subranshu Patel <spatel.ml@gmail.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Large buffer cache in EXT4
Date: Sun, 17 Feb 2013 11:19:11 +0100	[thread overview]
Message-ID: <201302171119.11371.Martin@lichtvoll.de> (raw)
In-Reply-To: <6F61E227-A6F7-4AD6-9B9C-39E9E9EAABFA@dilger.ca>

Am Sonntag, 17. Februar 2013 schrieb Andreas Dilger:
> On 2013-02-16, at 21:04, Subranshu Patel <spatel.ml@gmail.com> wrote:
> > I created 2 filesystem on my system (RHEL 6.3, kernel version 2.6.32)
> > - XFS and EXT4 and mounted them.
> > 
> > On both the filesystem I executed the mdtest tool(opensource tool) for
> > 64 concurrent process. Each process performed the following:
> > - Create large number of directories
> > - Remove all the directories
> > 
> > During this time I monitored the memory usage of the system using sar
> > command. I checked the 3 components - kbmemused, kbbuffers and
> > kbcached
> > 
> > kbmemused - Amount of used memory in kilobytes. This does not take
> > into account memory used by the kernel itself.
> > kbbuffers - buffer cache
> > kbcached - page cache
> > 
> > While the kbmemused and kbcached component was almost similar in EXT4
> > and XFS (XFS being a little higher), the kbbuffer showed a totally
> > different trend.
> > 
> > For EXT4, kbbuffers was:
> > 390999KB for dir creation
> > 364803KB for dir removal
> > For XFS, kbbuffers was:
> > 
> > 1701KB for dir creation
> > 2738KB for dir removal
> > 
> > In kernel 2.6, both buffer cache and page cache are merged. The page
> > cache caches pages of files. The buffer cache caches disk blocks which
> > consists of mainly metadata (not file data).
> > 
> > Why is the buffer cache large in case of EXT4 and what is stored in
> > the buffer cache?
> 
> XFS does not use buffer cache, while ext[234] does use buffer cache.
> 
> This is just a different code design. Ext4 uses the buffer cache to track
> metadata for journaling.

Doesn´t XFS use its own mechanism with xfsbufd kernel thread?

Thanks,
-- 
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

  reply	other threads:[~2013-02-17 10:19 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 [this message]
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

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=201302171119.11371.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=spatel.ml@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox