Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: alex chen <alex.chen@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: add a mount option journal_async_commit on ocfs2 filesystem
Date: Wed, 7 Jan 2015 10:19:14 +0800	[thread overview]
Message-ID: <54AC97A2.5080707@huawei.com> (raw)
In-Reply-To: <20150106155832.27f4fe62123215f4ef8bc909@linux-foundation.org>


On 2015/1/7 7:58, Andrew Morton wrote:
> On Thu, 25 Dec 2014 10:53:05 +0800 alex chen <alex.chen@huawei.com> wrote:
> 
>> Add a mount option to support JBD2 feature:
>> JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT. When this feature is opened,
>> journal commit block can be written to disk without waiting for
>> descriptor blocks, which can improve journal commit performance. This
>> option will enable 'journal_checksum' internally.
>>
>> Using the fs_mark benchmark, using journal_async_commit shows a 50%
>> improvement, the files per second go up from 215.2 to 317.5.
>>
>> test script:
>> fs_mark  -d  /mnt/ocfs2/  -s  10240  -n  1000
>>
>> default:
>> FSUse%        Count         Size    Files/sec     App Overhead
>>      0         1000        10240        215.2            17878
>>
>> with journal_async_commit option:
>> FSUse%        Count         Size    Files/sec     App Overhead
>>      0         1000        10240        317.5            17881
> 
> For some reason this patch is a bit mangled and I had to apply the
> first hunk by hand.
> 

Sorry for my mistake? I will send the new patch based on linux-next
kernel. Thanks.
Alex
>>  fs/ocfs2/ocfs2.h |  2 ++
>>  fs/ocfs2/super.c | 17 +++++++++++++++++
> 
> Documentation/filesystems/ocfs2.txt needs an update.
OK
> 
> 
> 
> .
> 

      reply	other threads:[~2015-01-07  2:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-25  2:53 [Ocfs2-devel] [PATCH] ocfs2: add a mount option journal_async_commit on ocfs2 filesystem alex chen
2015-01-06 23:58 ` Andrew Morton
2015-01-07  2:19   ` alex chen [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=54AC97A2.5080707@huawei.com \
    --to=alex.chen@huawei.com \
    --cc=ocfs2-devel@oss.oracle.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