linux-kernel - Re: A mainline question about cgroup writeback

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] [day] [month] [year] [list]

Message-ID: <571891E0.60703@huawei.com>
Date:	Thu, 21 Apr 2016 16:40:00 +0800
From:	zhong jiang <zhongjiang@...wei.com>
To:	Tejun Heo <tj@...nel.org>
CC:	Miao Xie <miaoxie@...wei.com>, <lizefan@...wei.com>,
	<dingxiang@...wei.com>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: A mainline question about cgroup writeback

On 2016/4/21 5:22, Tejun Heo wrote:
> On Tue, Apr 19, 2016 at 03:19:59PM +0800, zhong jiang wrote:
>> cgroup writeback support the filesystem both ext4 and ext2.
>> but,  it appears to be not work when I test the function in the ext4.
>> The example is as follows:
>> echo "8:0 1048576" > blkio.throttle.write_bps_device
>> echo $$ > cgroup.procs
>> dd if=/dev/zero of=/test.c bs=1M count=10240
>> 10240+0 records in
>> 10240+0 records out
>> 10737418240 bytes (11 GB) copied, 49.8796 s, 215 MB/s
> How much memory does the cgroup have available to it?  It's buffered
> write.  It might not get throttled if there are enough pages to dirty.
>
> Thanks.
>
  Maybe it's my fault.  I just limit two fields in dirty_background_bytes and dirty_bytes , 
  and I don't consider about  the available memory in the cgroup.


 Thanks
 zhongjiang