Commit 0d4dde1a authored Apr 25, 2012 by Frederic Weisbecker Committed by Tejun Heo Apr 27, 2012

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>

parent 4d8438f0

kernel/res_counter.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -35,7 +35,7 @@ int res_counter_charge_locked(struct res_counter *counter, unsigned long val,
		}

		counter->usage += val;
		if (!force && counter->usage > counter->max_usage)
		if (counter->usage > counter->max_usage)
		counter->max_usage = counter->usage;
		return ret;
		}

Admin message