summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorLaura Abbott <lauraa@codeaurora.org>2012-09-12 09:36:16 +0200
committerChanho Park <chanho61.park@samsung.com>2014-11-18 11:42:20 +0900
commita253489daf66edd5e642a3971f80be6fdab4d048 (patch)
tree66d3d9c33207d91e5a612cece11193738cc61111 /drivers
parent272c66d0c0e5fd3f1a68dc366c233ae59869766e (diff)
downloadlinux-3.10-a253489daf66edd5e642a3971f80be6fdab4d048.tar.gz
linux-3.10-a253489daf66edd5e642a3971f80be6fdab4d048.tar.bz2
linux-3.10-a253489daf66edd5e642a3971f80be6fdab4d048.zip
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. Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions