RGBCube/Site
1
Fork 0
mirror of https://github.com/RGBCube/Site synced 2025-07-30 12:37:50 +00:00
Code Issues Activity Actions

dump(posix.fsync-pitfalls): update

Browse source
This commit is contained in:
RGBCube 2025-07-11 23:43:49 +03:00
parent a765c5fadc
commit 1116a3d797
Signed by: RGBCube
SSH key fingerprint: SHA256:CzqbPcfwt+GxFYNnFVCqoN5Itn4YFrshg1TrnACpA5M
1 changed files with 1 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
site/dump/posix/fsync-pitfalls.md
View file

@ -79,6 +79,7 @@ the list of pointers to disk.
- [(stackoverflow) Difference between `syncfs` (Linux only) and `fsync` (POSIX)](https://stackoverflow.com/questions/48171855/what-is-the-difference-between-fsync-and-syncfs)
(TL;DR: `syncfs` is "pretty please" fsync and doesn't block until the
operation is done)
- [(transactional.blog) Userland Disk I/O](https://transactional.blog/how-to-learn/disk-io)
- [(LWN) Feathersticth: Killing `fsync` softly](https://lwn.net/Articles/354861/)
- [(stackoverflow) Your Program ---~~`fflush`~~---> Your OS ---~~`fsync`~~---> Your Disk](https://stackoverflow.com/questions/2340610/difference-between-fflush-and-fsync)
- [(despairlabs) `fsync()` after `open()` is an elaborate no-op](https://despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op/)