On Wed, Oct 02, 2024 at 11:47:32AM -0400, Martin K. Petersen wrote: > It is the kernel's job to manage the system's hardware resources and > arbitrate and share these resources optimally and fairly between all > running applications. Exactly. > What irks me is defining application interfaces which fundamentally tell > the kernel that "these blocks are part of the same file". > > The kernel already knows this. It is the very entity which provides that > abstraction. Why do we need an explicit interface to inform the kernel > that concurrent writes to the same file should have the same > "temperature" or need to go to the same "bin" on the storage device? > Shouldn't that just happen automatically? For file: yes. The problem is when you have more files than buckets on the device or file systems. Typical enterprise SSDs support somewhere between 8 and 16 write streams, and there typically is more data than that. So trying to group it somehow is good idea as not all files can have their own bucket. Allowing this inside a file like done in this patch set on the other hand is pretty crazy. > Whether it's SCSI groups, streams, UFS hints, or NVMe FDP, it seems like > we are consistently failing to deliver something that actually works for > anything but a few specialized corner cases. I think that is a shame. Yes, it is. And as someone who has been sitting in this group that is because it's always someone in a place of power forcing down their version because they got a promotіon, best of show award or whatever.
