res_counter: Account max_usage when calling res_counter_charge_nofail()
authorFrederic Weisbecker <fweisbec@gmail.com>
Tue, 24 Apr 2012 23:11:36 +0000 (01:11 +0200)
committerTejun Heo <tj@kernel.org>
Fri, 27 Apr 2012 21:37:09 +0000 (14:37 -0700)
commit0d4dde1ac9a5af74ac76c6ab90557d1ae7b8f5d8
tree5e643c4d786b30814feec03f9731ea0d03c23fc4
parent4d8438f044d8aaac6fbba98316ba484dabea397d
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>
kernel/res_counter.c