diff options
| author | Frederic Weisbecker <fweisbec@gmail.com> | 2012-04-25 01:11:36 +0200 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2012-04-27 14:37:09 -0700 |
| commit | 0d4dde1ac9a5af74ac76c6ab90557d1ae7b8f5d8 (patch) | |
| tree | 5e643c4d786b30814feec03f9731ea0d03c23fc4 /Documentation/feature-removal-schedule.txt | |
| parent | 4d8438f044d8aaac6fbba98316ba484dabea397d (diff) | |
res_counter: Account max_usage when calling res_counter_charge_nofail()
Updating max_usage is something one would expect when we reach
a new maximum usage value even when we do this by forcing through
the limit with res_counter_charge_nofail().
(Whether we want to account failcnt when we force through the limit
is another debate).
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Acked-by: Glauber Costa <glommer@parallels.com>
Acked-by: Kirill A. Shutemov <kirill@shutemov.name>
Cc: Li Zefan <lizefan@huawei.com>
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
0 files changed, 0 insertions, 0 deletions