From: Hendrik Siedelmann <hendrik.siedelmann@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs raid allocator
Date: Tue, 06 May 2014 12:41:38 +0200 [thread overview]
Message-ID: <5368BC62.2020701@googlemail.com> (raw)
Hello all!
I would like to use btrfs (or anyting else actually) to maximize raid0
performance. Basically I have a relatively constant stream of data that
simply has to be written out to disk. So my question is, how is the
block allocator deciding on which device to write, can this decision be
dynamic and could it incorporate timing/troughput decisions? I'm willing
to write code, I just have no clue as to how this works right now. I
read somewhere that the decision is based on free space, is this still true?
Cheers
Hendrik
next reply other threads:[~2014-05-06 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:41 Hendrik Siedelmann [this message]
2014-05-06 10:59 ` Btrfs raid allocator Hugo Mills
2014-05-06 11:14 ` Hendrik Siedelmann
2014-05-06 11:19 ` Hugo Mills
2014-05-06 11:26 ` Hendrik Siedelmann
2014-05-06 11:46 ` Hugo Mills
2014-05-06 12:16 ` Hendrik Siedelmann
2014-05-06 20:59 ` Duncan
2014-05-06 21:49 ` Chris Murphy
2014-05-06 22:45 ` Hendrik Siedelmann
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=5368BC62.2020701@googlemail.com \
--to=hendrik.siedelmann@googlemail.com \
--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).