| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 30 Dec 2015 01:39:46 -0500 From: Sanidhya Solanki <jpage.lkml@...il.com> To: David Sterba <dsterba@...e.cz>, calestyo@...entia.net Cc: clm@...com, jbacik@...com, linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size On Tue, 29 Dec 2015 18:06:11 +0100 David Sterba <dsterba@...e.cz> wrote: > So you want to make the stripe size configurable?... As I see it there are 3 ways to do it: -Make it a compile time option that only configures it for a single system with any devices that are added to the RAID. -Make it a runtime option that can change based on how the administrator configures it. -A non-user facing option that is configurable by someone like a distribution maintainer for all systems using the Binary Distribution. As I see it, DS would like something like the third option, but CAM (ostensibly a SysAdmin) wants the second option. On the other hand, I implemented the first option. The first and third option can co-exit, the second is an orthogonal target that needs to be setup separately. Or we can make all options co-exist, but make it more complicated. Please let me know which implementation is preferable, and, if you just want me to expand the description (as DS' mail asked for) or redo the entire setup. Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists