Add NOCACHE_FLUSHALL environment variable and matching -f switch
to the nocache wrapper.
The rationale behind this are multiple:
some applications might know the files being processed will never stay
in cache; in this case the overhead of flushing them is just not worth it
(we have some 24TB (sparse) file for which the mincore check is rather
costly)
given the kernel does have some heuristics to not respect the fadv
dontneed hint, one could consider it's just as simple to leave the logic
to it
Hi! I've just found about this through #xfs@freenode, and it looks interesting; but needed something to skip the mincore for our use case.
Figured I could make it an option, and didn't see any issue/PR mentioning this so went ahead.
I've written [RFC] as it's mostly testing waters, I don't think I'd change much from this for a final version, but didn't want to spend time fiddling with details if people are against the idea.
Add NOCACHE_FLUSHALL environment variable and matching -f switch to the nocache wrapper.
The rationale behind this are multiple:
Hi! I've just found about this through #xfs@freenode, and it looks interesting; but needed something to skip the mincore for our use case. Figured I could make it an option, and didn't see any issue/PR mentioning this so went ahead. I've written [RFC] as it's mostly testing waters, I don't think I'd change much from this for a final version, but didn't want to spend time fiddling with details if people are against the idea.
Thanks!