On Wed, Dec 30, 2009 at 3:12 PM, Richard Elling <richard.ell...@gmail.com> wrote: > If the allocator can change, what sorts of policies should be > implemented? Examples include: > + should the allocator stick with best-fit and encourage more > gangs when the vdev is virtual? > + should the allocator be aware of an SSD's page size? Is > said page size available to an OS? > + should the metaslab boundaries align with virtual storage > or SSD page boundaries?
Wandering off topic a little bit... Should the block size be a tunable so that page size of SSD (typically 4K, right?) and upcoming hard disks that sport a sector size > 512 bytes? http://arc.opensolaris.org/caselog/PSARC/2008/769/final_spec.txt > And, perhaps most important, how can this be done automatically > so that system administrators don't have to be rocket scientists > to make a good choice? Didn't you read the marketing literature? ZFS is easy because you only need to know two commands: zpool and zfs. If you just ignore all the subcommands, options to those subcommands, evil tuning that is sometimes needed, and effects of redundancy choices then there is no need for any rocket scientists. :) -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
