> The NVMe protocol has extremely deep queues [1] and leaving them empty means leaving performance on the table. I think you'll find it surprisingly difficult to saturate the PCIe bus with just one core: PCIe 7 will support 512GB/s
is disk IO bottlenecked by NVMe/PCIe limits, or by disk iops limits?
> Unix FSs tend to store file_name to inode mappings per directory, so creating a new mapping in one directory doesn't interfere with another directory.
again, you're handwaving on what "interfere" means
do "inode mappings" represent resources with no shared resource constraints?
is reading one "inode mapping" as fast as you can with one core independent from reading a different "inode mapping" as fast as you can with a separate core?
is disk IO bottlenecked by NVMe/PCIe limits, or by disk iops limits?
> Unix FSs tend to store file_name to inode mappings per directory, so creating a new mapping in one directory doesn't interfere with another directory.
again, you're handwaving on what "interfere" means
do "inode mappings" represent resources with no shared resource constraints?
is reading one "inode mapping" as fast as you can with one core independent from reading a different "inode mapping" as fast as you can with a separate core?
afaik it is not, am i wrong?