On Mon, Jun 06, 2016 at 09:43:19AM -0400, Andrew Armenia wrote: > On Mon, Jun 6, 2016 at 5:17 AM, David Sterba <dste...@suse.cz> wrote: > > On Thu, Jun 02, 2016 at 09:50:15PM -0400, Andrew Armenia wrote: > >> This patch adds mount option 'chunk_width_limit=X', which when set forces > >> the chunk allocator to use only up to X devices when allocating a chunk. > >> This may help reduce the seek penalties seen in filesystems with large > >> numbers of devices. > > > > There is a use for such limit but passing it as a mount is not the right > > way to do it. Changing the value requires remount, different raid levels > > might need different values, it's not persistent etc. > > Thanks for the feedback. I agree that it's less than an ideal way to > do it. I guess I was a bit quick to release proof-of-concept code. > I'll try to do some more work on the configuration side of things and > resubmit.
Last time something like this came up in discussion, the consensus was to put the configuration in xattrs in the btrfs namespace. There should be one with a name to indicate "global" configuration, applied to the top of subvol 5. If the feature allows configuration on a per-subvol or per-object basis, then there should also be a name for the relevant xattr (also in the btrfs namespace) that can be created on each object as required. Hugo. -- Hugo Mills | Klytus, I'm bored. What plaything can you offer me hugo@... carfax.org.uk | today? http://carfax.org.uk/ | PGP: E2AB1DE4 | Ming the Merciless, Flash Gordon
signature.asc
Description: Digital signature
