Messages in this thread | | | Date | Mon, 31 Oct 2011 21:38:37 +0100 | Subject | ext4 bug ? "Intel 320 SSD write performance – cont d." | From | Vincent Pelletier <> |
| |
Hi.
Reading this blog post[1], I thought the "2nd iteration" results could be considered a bug in mkfs.ext4 (and possibly any mkfs implementation): shouldn't mkfs run [FI]TRIM on its target before creating filesystem structure ?
Disclaimers: I don't know much about mkfs nor in-kernel fs support to tell which part should implement this - so I cannot even tell for sure this isn't done already. I have no idea how expensive those new calls would be (in general, this means trimming a _lot_ of pages...). I don't know how other filesystems/os behave on such bench. But I don't think this is a problem any SSD could solve at its level.
[1] http://www.mysqlperformanceblog.com/2011/09/28/intel-320-ssd-write-performance-contd/
Regards, -- Vincent Pelletier
| |