linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] Revert "Btrfs: do not do filemap_write_and_wait_range in fsync"
Date: Thu, 13 Sep 2012 08:38:34 -0400	[thread overview]
Message-ID: <20120913123834.GC12994@localhost.localdomain> (raw)
In-Reply-To: <5051BB3B.5020201@cn.fujitsu.com>

On Thu, Sep 13, 2012 at 04:53:47AM -0600, Miao Xie wrote:
> This reverts commit 0885ef5b5601e9b007c383e77c172769b1f214fd
> 
> After applying the above patch, the performance slowed down because the dirty
> page flush can only be done by one task, so revert it.
> 
> The following is the test result of sysbench:
> 	Before		After
> 	24MB/s		39MB/s
> 

Ah I didn't think about that, good point, thanks!

Josef

      reply	other threads:[~2012-09-13 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 10:53 [PATCH 2/2] Revert "Btrfs: do not do filemap_write_and_wait_range in fsync" Miao Xie
2012-09-13 12:38 ` Josef Bacik [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=20120913123834.GC12994@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --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).