linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Florian D." <flockmock@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] Btrfs: a copy on write, snapshotting FS
Date: Sat, 16 Jun 2007 00:03:06 +0200	[thread overview]
Message-ID: <46730C9A.6090107@gmail.com> (raw)
In-Reply-To: <20070615205140.GV2061@think.oraclecorp.com>

Chris Mason wrote:
> Well, apparently I get get the silly stuff wrong an infinite number of
> times.  Sorry, lets try again:
> 
> diff -r 38b36aaaa731 disk-io.c
> --- a/disk-io.c	Fri Jun 15 13:50:20 2007 -0400
> +++ b/disk-io.c	Fri Jun 15 16:52:38 2007 -0400
> @@ -541,6 +541,8 @@ int write_ctree_super(struct btrfs_trans
>  	else
>  		ret = submit_bh(WRITE, bh);
>  	if (ret == -EOPNOTSUPP) {
> +		get_bh(bh);
> +		lock_buffer(bh);
>  		set_buffer_uptodate(bh);
>  		root->fs_info->do_barriers = 0;
>  		ret = submit_bh(WRITE, bh);
> 

ha! it is working now. some numbers from here(with the fio-tool):

1. sequential read
2. random writes
3. sequential read again

filesize:300MB, bs:4K

   btrfs                  reiserfs               ext3
   usr% sys% bw   sec.    usr% sys% bw   sec.    usr% sys% bw   sec.
1  5    51   68.3 4.6     1    17   67.4 4.6     5    24   68.0 4.6
2  0    1    0.7  431     2    21   29.8 10.5    3    18   29.0 10.8
3  0    1    2.3  133     1    19   70.5 4.4     5    24   68.6 4.5

bw: MB/sec.
ext3: -o data=writeback,barrier=1

20GB LVM2 partition on a RAID6 (4 SATA-disks)

cheers,
florian

  reply	other threads:[~2007-06-15 22:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 16:10 [ANNOUNCE] Btrfs: a copy on write, snapshotting FS Chris Mason
2007-06-12 19:53 ` Mike Snitzer
2007-06-12 20:14   ` Chris Mason
2007-06-13  3:08     ` Christoph Hellwig
2007-06-13 10:17       ` Chris Mason
2007-06-13  3:46 ` John Stoffel
2007-06-13 10:35   ` Chris Mason
2007-06-13 14:00     ` John Stoffel
2007-06-13 14:54       ` Chris Mason
2007-06-13 16:12         ` John Stoffel
2007-06-13 16:34           ` Chris Mason
2007-06-13 16:25         ` Grzegorz Kulewski
2007-06-14 18:20   ` Chuck Lever
2007-06-14 18:48     ` Chris Mason
2007-06-15 17:17       ` Chuck Lever
2007-06-14 18:29 ` Florian D.
2007-06-14 19:13   ` Chris Mason
2007-06-15 19:08     ` Florian D.
2007-06-15 19:11       ` Chris Mason
2007-06-15 20:46         ` Florian D.
2007-06-15 20:51           ` Chris Mason
2007-06-15 22:03             ` Florian D. [this message]
2007-06-16  0:54               ` Chris Mason
2007-06-16  9:31                 ` Florian D.
2007-06-18 14:29                   ` Chris Mason
2007-06-18 14:41 ` Chris Mason
2007-06-18 17:37 ` Vladislav Bolkhovitin
2007-06-18 20:08   ` John Stoffel
2007-06-19  9:11   ` Pádraig Brady
2007-06-19 10:01     ` Vladislav Bolkhovitin
2007-06-19 18:20       ` david
2007-06-20  8:41         ` Vladislav Bolkhovitin
2007-06-19 12:04     ` Chris Mason
2007-06-19 14:00       ` Vladislav Bolkhovitin
2007-06-19 18:24       ` david
2007-06-19 18:28       ` Philipp Matthias Hahn
2007-06-20  8:44         ` Vladislav Bolkhovitin
2007-06-20  9:18           ` Ph. Marek
  -- strict thread matches above, loose matches on Subject: below --
2007-06-13  5:45 Albert Cahalan
2007-06-13 12:00 ` Chris Mason
2007-06-13 16:14   ` Albert Cahalan
2007-06-13 16:57     ` Chris Mason
2007-06-14  6:59       ` Albert Cahalan
2007-06-14 12:30         ` Chris Mason

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=46730C9A.6090107@gmail.com \
    --to=flockmock@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-fsdevel@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).