diff options
author | David Howells <dhowells@redhat.com> | 2016-02-01 16:43:04 (GMT) |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2016-02-01 17:30:10 (GMT) |
commit | a5b3a80b899bda0f456f1246c4c5a1191ea01519 (patch) | |
tree | b83e19613c5b5dfcf0311afef7d25e61b727bf74 /scripts/gcc-goto.sh | |
parent | 92e963f50fc74041b5e9e744c330dca48e04f08d (diff) | |
download | linux-a5b3a80b899bda0f456f1246c4c5a1191ea01519.tar.xz |
CacheFiles: Provide read-and-reset release counters for cachefilesd
Provide read-and-reset objects- and blocks-released counters for cachefilesd
to use to work out whether there's anything new that can be culled.
One of the problems cachefilesd has is that if all the objects in the cache
are pinned by inodes lying dormant in the kernel inode cache, there isn't
anything for it to cull. In such a case, it just spins around walking the
filesystem tree and scanning for something to cull. This eats up a lot of
CPU time.
By telling cachefilesd if there have been any releases, the daemon can
sleep until there is the possibility of something to do.
cachefilesd finds this information by the following means:
(1) When the control fd is read, the kernel presents a list of values of
interest. "freleased=N" and "breleased=N" are added to this list to
indicate the number of files released and number of blocks released
since the last read call. At this point the counters are reset.
(2) POLLIN is signalled if the number of files released becomes greater
than 0.
Note that by 'released' it just means that the kernel has released its
interest in those files for the moment, not necessarily that the files
should be deleted from the cache.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Steve Dickson <steved@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'scripts/gcc-goto.sh')
0 files changed, 0 insertions, 0 deletions