linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
	Itaru Kitayama <kitayama@cl.bb4u.ne.jp>
Subject: Re: [PATCH V2] btrfs: implement delayed inode items operation
Date: Thu, 17 Feb 2011 20:09:00 -0500	[thread overview]
Message-ID: <1297991261-sup-6831@think> (raw)
In-Reply-To: <4D5CB6B8.2060804@cn.fujitsu.com>

Excerpts from Miao Xie's message of 2011-02-17 00:48:40 -0500:
> Compare with Ext3/4, the performance of file creation and deletion on btrfs
> is very poor. the reason is that btrfs must do a lot of b+ tree insertions,
> such as inode item, directory name item, directory name index and so on.
> 
> If we can do some delayed b+ tree insertion or deletion, we can improve the
> performance, so we made this patch which implemented delayed directory name
> index insertion/deletion and delayed inode update.

This work is really cool, thanks for doing it.  I'm starting a run on
this tonight and if all goes well I'll review in detail and try to queue
it along with the per-subvolume storage bits for .39.

Thanks!

-chris

  reply	other threads:[~2011-02-18  1:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  5:48 [PATCH V2] btrfs: implement delayed inode items operation Miao Xie
2011-02-18  1:09 ` Chris Mason [this message]
2011-02-18  9:08   ` Miao Xie
2011-02-18 12:19     ` Chris Mason
2011-02-18 13:09       ` Miao Xie
2011-02-18 14:35         ` Chris Mason
2011-02-22  9:58           ` Miao Xie
2011-03-05  3:44   ` David Nicol
2011-02-18 13:30 ` David Sterba
2011-02-18 14:13   ` Miao Xie
  -- strict thread matches above, loose matches on Subject: below --
2011-02-24 14:02 Itaru Kitayama
2011-03-03  6:15 ` Miao Xie
2011-03-05  2:35   ` Itaru Kitayama

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=1297991261-sup-6831@think \
    --to=chris.mason@oracle.com \
    --cc=kitayama@cl.bb4u.ne.jp \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miaox@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).