All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <liubo2009@cn.fujitsu.com>
To: Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: Chris Samuel <chris@csamuel.org>,
	linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>,
	Josef Bacik <josef@redhat.com>, Arne Jansen <sensille@gmx.net>,
	David Sterba <dsterba@suse.cz>
Subject: Re: [RFC PATCH 0/5] apply rwlock for extent state
Date: Thu, 22 Mar 2012 09:17:30 +0800	[thread overview]
Message-ID: <4F6A7DAA.6050203@cn.fujitsu.com> (raw)
In-Reply-To: <4F6A7A8D.7060508@csamuel.org>

On 03/22/2012 09:04 AM, Chris Samuel wrote:
> On 21/03/12 23:34, Andrea Gelmini wrote:
> 
>> No comment, but I'm using this patches without problem since you
>> published it (compressed /home with hourly snapshot delete/creation).
> 
> Well worth sending a Tested-By: tag then, it's useful information.
> 
> cheers,
> Chris


Besides a Tested-By: tag, I'll appreciate a lot if anyone can provide
improvement/regression on performance with this patchset ;)

thanks,
liubo

  reply	other threads:[~2012-03-22  1:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  9:12 [RFC PATCH 0/5] apply rwlock for extent state Liu Bo
2012-03-15  9:12 ` [PATCH 1/5] Btrfs: use radix tree for checksum Liu Bo
2012-03-15  9:12 ` [PATCH 2/5] Btrfs: merge adjacent states as much as possible Liu Bo
2012-03-15  9:12 ` [PATCH 3/5] Btrfs: use large extent range for read and its endio Liu Bo
2012-03-15  9:12 ` [PATCH 4/5] Btrfs: apply rwlock for extent state Liu Bo
2012-03-15  9:12 ` [PATCH 5/5] Btrfs: avoid splitting state when truncating pagecache Liu Bo
2012-03-21  2:52 ` [RFC PATCH 0/5] apply rwlock for extent state Liu Bo
2012-03-21 12:34   ` Andrea Gelmini
2012-03-22  1:04     ` Chris Samuel
2012-03-22  1:17       ` Liu Bo [this message]
2012-03-22 13:09         ` Josef Bacik

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=4F6A7DAA.6050203@cn.fujitsu.com \
    --to=liubo2009@cn.fujitsu.com \
    --cc=andrea.gelmini@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=chris@csamuel.org \
    --cc=dsterba@suse.cz \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sensille@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.