"Theodore Ts'o" <ty...@mit.edu> writes: > I do think that using TRIM in various causes where we are doing an > fallocate does make sense for non-rotational devices. In general TRIM > should be fast enough that that I'd be surprised that people would be > complaining --- especially since most of the time, fallocate isn't on > the timing-critical path of most applications.
TRIM/UNMAP isn't just supported on solid state devices, though. I do recall some enterprise thinly provisioned storage that would take ages to discard large regions. I think that caused us to change the defaults for mkfs, right? Cheers, Jeff
