On Thu, Mar 09, 2023 at 08:11:35AM -0500, James Bottomley wrote: > On Thu, 2023-03-09 at 09:04 +0100, Javier González wrote: > > FTL designs are complex. We have ways to maintain sector sizes under > > 64 bits, but this is a common industry problem. > > > > The media itself does not normally oeprate at 4K. Page siges can be > > 16K, 32K, etc. > > Right, and we've always said if we knew what this size was we could > make better block write decisions. However, today if you look what > most NVMe devices are reporting, it's a bit sub-optimal: Your sample size may be off if your impression is that "most" NVMe drives report themselves this way. :) > jejb@lingrow:/sys/block/nvme1n1/queue> cat logical_block_size > 512 > jejb@lingrow:/sys/block/nvme1n1/queue> cat physical_block_size > 512 > jejb@lingrow:/sys/block/nvme1n1/queue> cat optimal_io_size > 0 > > If we do get Linux to support large block sizes, are we actually going > to get better information out of the devices? > > > Increasing the block size would allow for better host/device > > cooperation. As Ted mentions, this has been a requirement for HDD and > > SSD vendor for years. It seems to us that the time is right now and > > that we have mechanisms in Linux to do the plumbing. Folios is > > ovbiously a big part of this. > > Well a decade ago we did a lot of work to support 4k sector devices. > Ultimately the industry went with 512 logical/4k physical devices > because of problems with non-Linux proprietary OSs but you could still > use 4k today if you wanted (I've actually still got a working 4k SCSI > drive), so why is no NVMe device doing that? In my experience, all but the cheapest consumer grade nvme devices report 4k logical. They all support an option to emulate 512b if you really wanted it to, but the more optimal 4k is the most common default for server grade nvme.
