On Wed, Jul 07, 2010 at 09:53:30AM +0200, Lukas Czerner wrote: > > Hi all, > > since my last post I have done some more testing with various SSD's and the > trend is clear. Trim performance is getting better and the performance loss > without trim is getting lower. So I have decided to abandon the initial idea > to track free blocks within some internal data structure - it takes time and > memory. Do you have some numbers about how bad trim actually might be on various devices? I can imagine some devices where it might be better (for wear levelling and better write endurance if nothing else) where it's better to do the trim right away instead of batching things. So what I'm thinking about doing is keeping the "discard" mount option to mean non-batched discard. If you want to use the explicit FITRIM ioctl, I don't think we need to test to see if the dicard mount option is set; if the user issues the ioctl, then we should do the batched discard, and if we don't trust the user to do that, then well, the ioctl should be restricted to privileged users only --- especially if it could take up to a minute. - Ted -- 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
