linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Chris Mason <chris.mason@oracle.com>,
	linux-btrfs@vger.kernel.org,
	Arjan van de Ven <arjan@linux.intel.com>,
	"Wu, Fengguang" <fengguang.wu@intel.com>
Subject: Re: [patch 1/2]btrfs: add an ioctl to dump metadata info
Date: Tue, 20 Jul 2010 08:37:30 +0800	[thread overview]
Message-ID: <20100720003730.GA14218@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20100719112705.GX8623@think>

On Mon, Jul 19, 2010 at 07:27:05PM +0800, Chris Mason wrote:
> On Wed, Jul 14, 2010 at 04:02:21PM +0800, Shaohua Li wrote:
> > Add an ioctl to dump btrfs btree_inode's existing pages. Userspace collects such
> > info and uses it to do metadata readahead.
> 
> In your tests, how often is the mincore done on metadata?  With cow
> (especially with cow and atime), the metadata blocks are going to change
> quite a lot.
Meego uses relatime. The proposal is doing mincore in every boot. In my test,
I delete several files and a dir, create a dir and several files, the hit rate
is > 80%, which is already pretty good for boot. In userspace, we record some
extra pages. For example, if mincore returns two pages 2 and 4, userspace will
record pages 2-4, in total 3 pages, this will slightly increase hit rate too.

Thanks,
Shaohua

      reply	other threads:[~2010-07-20  0:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14  8:02 [patch 1/2]btrfs: add an ioctl to dump metadata info Shaohua Li
2010-07-19 11:27 ` Chris Mason
2010-07-20  0:37   ` Shaohua Li [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=20100720003730.GA14218@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=chris.mason@oracle.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).