On 24/04/10 02:41 PM, Ric Wheeler wrote: ..
I don't like the user space wiper.sh approach in general, but running wiper.sh is entirely your choice. Most users prefer having the file system and the IO stack take care of this for them, but again, entirely configurable.
.. I wrote wiper.sh, and I would prefer more of an in-kernel solution, simply because it could potentially have the smarts to deal with RAID, LVM, and btrfs's own duplicate implementation of RAID/LVM. Those cannot be done from userspace on a mounted filesystem. So.. again.. in an ideal kernel, I'd like to see use of larger ranges (and _multiple_ ranges) per TRIM command. And options for the kernel to do it automatically (-o discard), as well as an ioctl() interface for userspace to "scrub" (or "wipe") all free ranges in a gradual fashion. Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
