From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Subvolume level allocation policy
Date: Mon, 24 Oct 2011 11:44:16 +0200 [thread overview]
Message-ID: <4EA53370.1060909@jan-o-sch.net> (raw)
In-Reply-To: <4EA4620A.3060702@cfl.rr.com>
On 23.10.2011 20:50, Phillip Susi wrote:
> Is it ( yet? ) possible to manipulate the allocation policy on a
> subvolume level instead of the fs level? For example, to make / use
> raid1, and /home use raid0? Or to have / allocated from an ssd and
> /home allocated from the giant 2tb hd.
At least the latter can be achieved with speed profiles. I worked on
those together with Arne Jansen who sent patches in January 2011,
subject "[PATCH] Btrfs: introducing speed profiles and dedicated log
devices".
I don't assume they apply nowadays without a major rework, though. We
should get those patches merged sometime.
-Jan
prev parent reply other threads:[~2011-10-24 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 18:50 Subvolume level allocation policy Phillip Susi
2011-10-23 18:52 ` Hugo Mills
2011-10-24 9:44 ` Jan Schmidt [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=4EA53370.1060909@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=psusi@cfl.rr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.