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.thro
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.p
It looks like a bug on cgroup writeback. Is this a regression or
consistent issue? If it's a regression, you may could do bisect to
find out the buggy commit.
On Tue, Apr 19, 2016 at 3:19 PM, zhong jiang wrote:
> cgroup writeback support the filesystem both ext4 and ext2.
> but, it appears to be
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
10
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
10
5 matches
Mail list logo