previous: >>108805935
#define __NR_fadvise64 221
https://man7.org/linux/man-pages/man2/fadvise64.2.html
tl;dr:
advise the kernel as to how you plan to access a file
this is kind of gross:
The implementation may attempt to write back dirty pages in
the specified region, but this is not guaranteed. Any
unwritten dirty pages will not be freed. If the
application wishes to ensure that dirty pages will be
released, it should call fsync(2) or fdatasync(2) first.
either write them back, or else discard them all. don't tell me they may or may not get written back. the indeterminism is frightening
not something i've ever had occasion to use, but i can see where it would be useful
relevant resources:
man man
man syscalls
https://man7.org/linux/man-pages/
https://linux.die.net/man/
https://elixir.bootlin.com/linux/
https://elixir.bootlin.com/musl/
https://elixir.bootlin.com/glibc/