3 ms·
Yes, POSIX compatibility is the culprit for many of the issues we have with filesystems today. The POSIX requirements were made in and for a different world.
by eru 4y ago
Yes, POSIX compatibility is the culprit for many of the issues we have with filesystems today.
The POSIX requirements were made in and for a different world.
For example they also completely break down for distributed network filesystems. (Or at least destroy your hope of performance.)
- josephg 4y agoPOSIX doesn't stop linux from introducing new, non-posix APIs. Eg, io_uring isn't part of POSIX but linux has it anyway. As far as I can tell, an API for write barriers, grouped writes, transactional writes or iocp should be able to work alongside the POSIX API just fine. Its just another API for writing files which user programs can opt in to using.
- eru 4y agoYes, though for most practical file systems you still get hit by essentially having to also provide a POSIX compatible API.
- bheadmaster 4y agoThey break down performance for programs that expect zero-latency filesystem and access it in C-style sequential fashion. If we rewrite all UNIX utilities to be concurrent by default, the file API wouldn't make things that much worse.