diff options
| author | Jinshan Xiong <[email protected]> | 2016-09-18 16:38:15 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2016-09-19 09:51:51 +0200 |
| commit | 08fd034670b505c0ce1685404acaed0a4c073ef9 (patch) | |
| tree | 75d83173da43675674477e57965bfca3353a6699 /tools/perf/scripts/python/bin | |
| parent | eda3565c3654fe98b2f7b61db0ad0307672fa25d (diff) | |
staging: lustre: ldlm: revert the changes for lock canceling policy
The changes for LRU lock policy was introduced by commit bfae5a4e,
where I was trying to revise the policy to pick locks for canceling.
However, this caused two problems as mentioned in LU-5727. The first
problem is that the lock can only be picked for canceling only if
the number of LRU locks is over preset LRU number AND it's aged; the
second problem is that mdc_cancel_weight() tends to not cancel OPEN
locks, therefore open locks can be kept forever and finally exhausts
memory on the MDT side.
The commit 7b2d26b0 ("revert changes to ldlm_cancel_aged_policy") fixed
the first problem. This patch will revert the rest of changes related
to LRU policy revise.
Signed-off-by: Jinshan Xiong <[email protected]>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5727
Reviewed-on: http://review.whamcloud.com/12733
Reviewed-by: Niu Yawei <[email protected]>
Reviewed-by: Bobi Jam <[email protected]>
Reviewed-by: Oleg Drokin <[email protected]>
Signed-off-by: James Simmons <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions