All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Miao Xie <miaoxie@huawei.com>, <lizefan@huawei.com>,
	<dingxiang@huawei.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: A mainline question about cgroup writeback
Date: Thu, 21 Apr 2016 16:40:00 +0800	[thread overview]
Message-ID: <571891E0.60703@huawei.com> (raw)
In-Reply-To: <20160420212251.GF4775@htj.duckdns.org>

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

  reply	other threads:[~2016-04-21  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  7:19 A mainline question about cgroup writeback zhong jiang
2016-04-20  6:32 ` Alex Shi
2016-04-20 21:22 ` Tejun Heo
2016-04-21  8:40   ` zhong jiang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-18 12:53 zhong jiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=571891E0.60703@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=dingxiang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=miaoxie@huawei.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.