linux-kernel - Re: [PATCH] Add the max_usage member on the res

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080311214034.d2cae354.akpm@linux-foundation.org>
Date:	Tue, 11 Mar 2008 21:40:34 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Pavel Emelyanov <xemul@...nvz.org>
Cc:	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Add the max_usage member on the res_counter

On Tue, 11 Mar 2008 17:55:46 +0300 Pavel Emelyanov <xemul@...nvz.org> wrote:

> This field is the maximal value of the usage one since the counter
> creation (or since the latest reset).
> 
> To reset this to the usage value simply write anything to the
> appropriate cgroup file.

What is the justification for making this change?  Why do we need it? 
Please provide this information for all patches where it is not obvious.

>  	{
> +		.name = "max_usage_in_bytes",
> +		.private = RES_MAX_USAGE,
> +		.write = mem_cgroup_max_reset,
> +		.read_u64 = mem_cgroup_read,
> +	},

Documentation/controllers/memory.txt needs updating.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/