mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: 张真 <zhangzhen507@163.com>
Cc: aaronlee0817@163.com, axboe@kernel.dk, mlin@kernel.org,
	shli@kernel.org, linux-kernel@vger.kernel.org,
	cgroup@vger.kernel.org, linux-block@vger.kernel.org,
	zhen1.zhang@samsung.com, yanzi.zhang@samsung.com,
	jiale0817.li@samsung.com
Subject: Re: Cgroup: iops throttle problem
Date: Wed, 20 Jul 2016 11:30:52 -0400	[thread overview]
Message-ID: <20160720153052.GE4574@htj.duckdns.org> (raw)
In-Reply-To: <3aad6640.14fc7.155fe37ba10.Coremail.zhangzhen507@163.com>

Hello,

On Mon, Jul 18, 2016 at 09:35:12PM +0800, 张真 wrote:
> Hello
> My name is Zhen Zhang , me and Jiale Li recently test and analyze the cgroup
> blkio functions.
> We tested the buffered read a file using bio when the 
> blkio.throttle.read_iops_device is set 1000.
> The fio result file displays the iops is 13720 larger than 1000 when blocksize 
> is 4K in fio.

blk-throttle does allow bursts so the iops might go over the set limit
for a short period.  Over time, it shouldn't be over the set limit.

> We set different blocksize in fio:
> 4K, 8K , 16K, 32K, 64K, 128K, 256K, 512K, 1024K
> 
> The iops in fio:
> 13035, 7258, 3711, 1698, 907, 460, 228, 102, 54

Looks like you were hitting the natural bandwidth limit of the device.

> When bs is less than 64K, the iops is larger than 1000, when bs is larger than
> 64K, the iops is less than 1000.
> We tested it on ubuntu 16.04 with kernel 4.4.0
> 
> Dose this a problem of blkio iops throttle?

I don't know how the test was run but consistently going over the set
limit isn't the expected behavior.

Thanks.

-- 
tejun

      reply	other threads:[~2016-07-20 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 13:35 张真
2016-07-20 15:30 ` Tejun Heo [this message]

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=20160720153052.GE4574@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=aaronlee0817@163.com \
    --cc=axboe@kernel.dk \
    --cc=cgroup@vger.kernel.org \
    --cc=jiale0817.li@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlin@kernel.org \
    --cc=shli@kernel.org \
    --cc=yanzi.zhang@samsung.com \
    --cc=zhangzhen507@163.com \
    --cc=zhen1.zhang@samsung.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®