linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olivier Bonvalet <btrfs.list@daevel.fr>
To: Daniel Pocock <daniel@pocock.com.au>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: raw partition or LV for btrfs?
Date: Tue, 14 Aug 2012 15:52:04 +0200	[thread overview]
Message-ID: <502A5804.7080003@daevel.fr> (raw)
In-Reply-To: <502A529B.8060201@pocock.com.au>

On 14/08/2012 15:28, Daniel Pocock wrote:
> If I create 10 LVs today, with btrfs on each,


 From my understanding of Btrfs, it achieve good write performance by 
making near all writes "sequential". But if you split your disk in 10 
sub-parts, and set btrfs on each of them, writes operations of Btrfs 
will not really be sequential anymore.

So, for me, to have good performance btrfs should manage all the disk
(maybe excepting the /boot/ directory, just to avoid any problem with grub).

  reply	other threads:[~2012-08-14 13:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-12 16:46 raw partition or LV for btrfs? Daniel Pocock
2012-08-12 22:48 ` Fajar A. Nugraha
2012-08-13  4:19   ` Kyle Gates
2012-08-13  4:49     ` Fajar A. Nugraha
2012-08-14 11:23   ` Calvin Walton
2012-08-22 15:42     ` David Sterba
2012-08-28 11:54       ` raw partition or LV for btrfs? (FAQ updated) Daniel Pocock
2012-08-14 13:28   ` raw partition or LV for btrfs? Daniel Pocock
2012-08-14 13:52     ` Olivier Bonvalet [this message]
2012-08-14 13:53     ` Fajar A. Nugraha
2012-08-14 14:09       ` cwillu
2012-08-14 14:21         ` Fajar A. Nugraha
2012-08-14 14:50           ` cwillu
2012-08-14 14:44         ` Calvin Walton

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=502A5804.7080003@daevel.fr \
    --to=btrfs.list@daevel.fr \
    --cc=daniel@pocock.com.au \
    --cc=linux-btrfs@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).