7 ms·

I found this recent thread interesting, specifically about really considering whether you're going to read the data you just wrote in the near future or not (in

I found this recent thread interesting, specifically about really considering whether you're going to read the data you just wrote in the near future or not (in which case, use direct IO) and a set of (abandoned?) patches for write-behind caching for sequential writes in Linux (https://lore.kernel.org/lkml/156896493723.4334.13340481207144634918.stgit@buzz/ https://lore.kernel.org/lkml/156896493723.4334.1334048120714...). https://lore.kernel.org/linux-mm/45odvhgymm7fxsgwpewoiiggaokxjcr7ootsamm4rwsdw26j62@5lohhv2kvofo/T/ https://lore.kernel.org/linux-mm/45odvhgymm7fxsgwpewoiiggaok...

rwmj 2y ago
Direct IO is very inflexible. A better way is this recommended by Linus in an old post: https://lkml.iu.edu/hypermail/linux/kernel/1005.2/01845.html https://lkml.iu.edu/hypermail/linux/kernel/1005.2/01845.html I implemented something along the same lines but a bit less spicy here: https://gitlab.com/nbdkit/nbdkit/-/commit/aa5a2183a6d16afd919174b5ba8222b2bccf4039 https://gitlab.com/nbdkit/nbdkit/-/commit/aa5a2183a6d16afd91...
- rwmj 2y ago
  That second link is wrong, should be: https://gitlab.com/nbdkit/nbdkit/-/commit/a956e2e75d6c88eeefecd967505667c9f176e3af https://gitlab.com/nbdkit/nbdkit/-/commit/a956e2e75d6c88eeef...