From: David Sterba <dsterba@suse.cz>
To: Toggenburger Lukas <Lukas.Toggenburger@htwchur.ch>
Cc: Tomasz Torcz <tomek@pipebreaker.pl>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Working on Btrfs as topic for master thesis
Date: Wed, 22 Jan 2014 13:05:33 +0100 [thread overview]
Message-ID: <20140122120533.GE6498@twin.jikos.cz> (raw)
In-Reply-To: <8E968DF3B7EC0D40B67B5A9D25675A6A0400BF@MBXSRV03EDU.edu.local>
On Sat, Jan 18, 2014 at 12:50:54PM +0000, Toggenburger Lukas wrote:
> Hello Tomasz
>
> > Have you considered per-file/per-directory selection of raid level?
>
> Sounds great, I haven't thought about it before.
>
> Do you or someone else know what the current state of development is?
> Is someone working on this?
The feature lacks interface to specify the raid flags per-object. This
is WIP, keyword is 'properties', you'll find some preliminary patches in
the list. This is the ground work for all sorts of fancy tuning.
The filesystem split into areas with different raid levels will bring
interesting problems regarding free space and operations that cross the
raid levels. But I think it's doable.
next prev parent reply other threads:[~2014-01-22 12:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 19:23 Working on Btrfs as topic for master thesis Toggenburger Lukas
2014-01-17 15:34 ` David Sterba
2014-01-17 16:04 ` Tomasz Torcz
2014-01-18 12:50 ` Toggenburger Lukas
2014-01-22 12:05 ` David Sterba [this message]
2014-01-22 13:35 ` Hugo Mills
2014-01-20 5:44 ` Roger Binns
2014-01-22 12:12 ` David Sterba
2014-01-22 20:55 ` Roger Binns
2014-01-23 18:36 ` David Sterba
2014-01-23 21:47 ` Roger Binns
2014-01-20 12:20 ` Austin S Hemmelgarn
2014-01-21 6:42 ` Sandy McArthur
2014-01-21 12:25 ` Austin S Hemmelgarn
2014-01-21 16:52 ` Hugo Mills
2014-01-21 16:59 ` Austin S Hemmelgarn
2014-01-22 12:20 ` David Sterba
2014-01-22 12:24 ` David Sterba
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=20140122120533.GE6498@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Lukas.Toggenburger@htwchur.ch \
--cc=linux-btrfs@vger.kernel.org \
--cc=tomek@pipebreaker.pl \
/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