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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=2t_tL=Vt4athAyQ1tDhLDGpqtmu-iAOjdbPBJ@mail.gmail.com>
Date:	Tue, 22 Mar 2011 10:06:27 -0700
From:	Ying Han <yinghan@...gle.com>
To:	Michal Hocko <mhocko@...e.cz>
Cc:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Daisuke Nishimura <nishimura@....nes.nec.co.jp>,
	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: cgroup: real meaning of memory.usage_in_bytes

On Tue, Mar 22, 2011 at 12:35 AM, Michal Hocko <mhocko@...e.cz> wrote:
> On Mon 21-03-11 10:22:41, Ying Han wrote:
> [...]
>>
>> Michal,
>>
>> Can you help to post the test result after applying the patch?
>
> The result of the LTP test is:
> TEST 4: MEMORY CONTROLLER TESTING
> RUNNING SETUP.....
> WARN:/dev/memctl already exist..overwriting
> Cleanup called
> TEST STARTED: Please avoid using system while this test executes
> memory usage from memory.usage_in_bytes= 62955520
> memory usage from memory.stat= 62955520
> TINFO   Memory Resource Controller: stat check test passes first run
> Test continues to run the second step.
> memory usage from memory.usage_in_bytes= 78643200
> memory usage from memory.stat=78643200
> TPASS   Memory Resource Controller: stat check test PASSED
> Memory Resource Controller test executed successfully.
> Cleanup called
>
> The attached simple test case result is:
> # mkdir /dev/memctl; mount -t cgroup -omemory cgroup /dev/memctl; cd /dev/memctl
> # mkdir group_1; cd group_1; echo 100M > memory.limit_in_bytes
> # cat memory.{usage_in_bytes,stat}
> 0
> cache 0
> rss 0
> [start the test case, add its pid to the group and let it fault in]
>
> # cat memory.{usage_in_bytes,stat}
> 4096
> cache 0
> rss 4096
>
> [let it finish]
> # cat memory.{usage_in_bytes,stat}
> 0
> cache 0
> rss 0
>
> Thanks

Thanks Michal for fixing it up. Regardless of the performance
overhead, the change make sense to me.

--Ying

> --
> Michal Hocko
> SUSE Labs
> SUSE LINUX s.r.o.
> Lihovarska 1060/12
> 190 00 Praha 9
> Czech Republic
>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ