From: Christoph Anton Mitterer <calestyo@scientia.net>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
Date: Tue, 05 Jan 2016 19:48:17 +0100 [thread overview]
Message-ID: <1452019697.5722.10.camel@scientia.net> (raw)
In-Reply-To: <20160105104455.GS4227@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On Tue, 2016-01-05 at 11:44 +0100, David Sterba wrote:
> We have a full 32 bit number space, so multiples of power of 2 are
> also
> possible if that makes sense.
Hmm that would make a maximum of 4GiB RAID chunks...
perhaps we should reserve some of the higher bits for a multiplier, in
case 4GiB would ever become too little O;-)
> In general we don't need to set additional
> limitations besides minimum, maximum and "minimal step".
And that can/should be done in the userland.
> > Are there any concerns/constraints with too small/too big chunks
> > when
> > these play together with lower block layers (I'd guess not).
>
> I don't think so.
Well I was mainly thinking about dm-crypt, that uses 512B blocks and in
fact that size wouldn't be easy to change, as (IIRC) larger block sizes
make XTS less secure.
Obviously *this* isn't anything that btrfs would have to worry about,
especially as we're anyway on a higher block layer level,.. but it just
reminded me that there can be cases where too large / too small may
actually cause issues.
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2016-01-05 18:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 12:24 [PATCH] BTRFS: Adds an option to select RAID Stripe size Sanidhya Solanki
2015-12-28 22:19 ` Christoph Anton Mitterer
2015-12-28 20:38 ` Sanidhya Solanki
2015-12-29 1:21 ` Christoph Anton Mitterer
2015-12-28 21:43 ` Sanidhya Solanki
2015-12-29 3:42 ` Christoph Anton Mitterer
2015-12-29 0:03 ` Sanidhya Solanki
2015-12-29 4:26 ` Christoph Anton Mitterer
2015-12-29 1:31 ` Sanidhya Solanki
2015-12-29 6:03 ` Christoph Anton Mitterer
2015-12-29 2:23 ` Sanidhya Solanki
2015-12-29 15:32 ` Christoph Anton Mitterer
2015-12-29 16:44 ` Duncan
2015-12-30 2:56 ` Christoph Anton Mitterer
2015-12-29 18:06 ` David Sterba
2015-12-30 20:00 ` Christoph Anton Mitterer
2015-12-30 21:02 ` Duncan
2015-12-30 21:13 ` Christoph Anton Mitterer
2016-01-02 11:52 ` Sanidhya Solanki
2016-01-03 1:37 ` Qu Wenruo
2016-01-03 2:26 ` Christoph Anton Mitterer
2016-01-05 10:44 ` David Sterba
2016-01-05 18:48 ` Christoph Anton Mitterer [this message]
2016-01-10 3:11 ` Sanidhya Solanki
2016-01-11 1:29 ` Qu Wenruo
2016-01-11 15:43 ` Christoph Anton Mitterer
2016-01-11 11:49 ` Sanidhya Solanki
2016-01-11 15:57 ` Christoph Anton Mitterer
2016-01-11 16:01 ` Hugo Mills
2016-01-12 12:23 ` Austin S. Hemmelgarn
2016-01-12 12:07 ` Sanidhya Solanki
2015-12-29 13:39 ` David Sterba
2015-12-29 11:15 ` Sanidhya Solanki
2015-12-29 17:06 ` David Sterba
2015-12-29 21:32 ` Sanidhya Solanki
2015-12-30 6:39 ` Sanidhya Solanki
2015-12-30 11:59 ` Qu Wenruo
2015-12-30 9:54 ` Sanidhya Solanki
2015-12-30 14:10 ` Qu Wenruo
2015-12-30 11:15 ` Sanidhya Solanki
2015-12-30 15:58 ` David Sterba
2015-12-30 21:19 ` Sanidhya Solanki
2015-12-30 16:17 ` David Sterba
2015-12-30 21:21 ` Sanidhya Solanki
2016-01-05 10:33 ` David Sterba
2015-12-31 0:46 ` Qu Wenruo
2016-01-05 10:16 ` David Sterba
2015-12-30 19:48 ` Christoph Anton Mitterer
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=1452019697.5722.10.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=dsterba@suse.cz \
--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).