summaryrefslogtreecommitdiff
path: root/fs/ecryptfs/Kconfig
diff options
context:
space:
mode:
authorLaura Abbott <lauraa@codeaurora.org>2012-08-30 18:01:17 -0700
committerKyle Yan <kyan@codeaurora.org>2016-06-01 15:20:51 -0700
commita2ac6d40d3395cac27257a72c52d4dbdde7428be (patch)
tree9520853f9da803980c8b4f957260b789f0c88efb /fs/ecryptfs/Kconfig
parent7099c2a6d2f6c68016bfdb2c62eefa49885b569c (diff)
fs/buffer.c: Revoke LRU when trying to drop buffers
When a buffer is added to the LRU list, a reference is taken which is not dropped until the buffer is evicted from the LRU list. This is the correct behavior, however this LRU reference will prevent the buffer from being dropped. This means that the buffer can't actually be dropped until it is selected for eviction. There's no bound on the time spent on the LRU list, which means that the buffer may be undroppable for very long periods of time. Given that migration involves dropping buffers, the associated page is now unmigratible for long periods of time as well. CMA relies on being able to migrate a specific range of pages, so these these types of failures make CMA significantly less reliable, especially under high filesystem usage. Rather than waiting for the LRU algorithm to eventually kick out the buffer, explicitly remove the buffer from the LRU list when trying to drop it. There is still the possibility that the buffer could be added back on the list, but that indicates the buffer is still in use and would probably have other 'in use' indicates to prevent dropping. Change-Id: I253f4ee2069e190c1115afc421dadd27a7fa87dc Signed-off-by: Laura Abbott <lauraa@codeaurora.org> Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
Diffstat (limited to 'fs/ecryptfs/Kconfig')
0 files changed, 0 insertions, 0 deletions