Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
An eternally recurring request from our benchmark team at Cray is an easy way from the client side to force the server to drop its cache. This is purely for benchmarking purposes, and of course must be limited to elevated users only.
I've written a small patch to add this functionality to ladvise, using an upcall on the server side. As it is currently, it is a pretty blunt instrument, in that it will cause all the OSSes where the file resides (i.e. which host any of the OSTs for the file) to call drop caches. However, this is by design, because the benchmarkers want to clean out everything on the server. (Again, this is not intended to be used during normal use of a system, but only by elevated users in specific circumstances.)
As it stands, this patch is RFC. I've tested it and verified it works, but there are a number of open questions/things to resolve.
1. Is ladvise the right place for this, even when requiring evelated permission?
2. Is the "call this on a file, and it will act on all OSSes responsible for parts of that file" the right interface? There is a clear opportunity to accept a striping pattern into the command, and then create a special hidden file (similar to migrate and some of the HSM functionality) and call the ioctl on that file. I chose not to do this because it seems like too much to bring the interface required to describe a setstripe operation into the ladvise interface
3. Details of how the script is packaged, named, etc.