Linux block layer
 help / color / mirror / Atom feed
From: aaronlee0817  <aaronlee0817@163.com>
To: "Tejun Heo" <tj@kernel.org>
Cc: axboe@kernel.dk, mlin@kernel.org, shli@kernel.org,
	linux-kernel@vger.kernel.org, cgroup@vger.kernel.org,
	jiale0817.li@samsung.com, yanzi.zhang@samsung.com,
	zhen1.zhang@samsung.com, linux-block@vger.kernel.org
Subject: Re:Re: cgroup: Fix split bio been throttled more than once
Date: Wed, 6 Jul 2016 22:58:55 +0800 (CST)	[thread overview]
Message-ID: <458d1946.12fa6.155c0b80d60.Coremail.aaronlee0817@163.com> (raw)
In-Reply-To: <20160705222626.GC25394@htj.duckdns.org>

[-- Attachment #1: Type: text/plain, Size: 2782 bytes --]

Hi Tejun Heo

>At 2016-07-06 06:26:26, "Tejun Heo" <tj@kernel.org> wrote:
>Hello,
>
>On Mon, Jul 04, 2016 at 10:46:54PM +0800, Jiale Li wrote:
>> These days, we have tested the cgroup blkio throttle function use fio,
>> and we found a problem that when we use buffered IO or set the big block
>> size like 1M, then the IO performance cannot reach the value we set.
>> For example we set blkio.throttle.read_bps_device as 10M, in kernel 
>> version 4.3 IO performance can only reach 6M, and in kernel version 
>> 4.4 the actual IO bps is only 3.1M. 
>> 
>> Then we did some research and find that in kernel version 4.3 brought in
>> blk_queue_split() function to split the big size bio into several parts,
>> and some of them are calling the generic_make_request() again, this result
>> the bio been throttled more than once. so the actual bio sent to device is 
>> less than we expected.
>> 
>> We have checked the newest kernel of 4.7-rc5, this problem is still exist.
>> 
>> Based on this kind of situation, we propose a fix solution to add a flag bit
>> in bio to let the splited bio bypass the blk_queue_split(). Below is the patch
>> we used to fix this problem.
>
>Thanks a lot for the report.  Hmmm... there was another brekage around
>split bios, I wonder whether the two can be handled together somehow.
>
> http://lkml.kernel.org/g/1466583730-28595-1-git-send-email-lars.ellenberg@linbit.com 


About this patch, I agree with Ming Lei, this is another issue, they are independent
of each other.
  
>
>> diff --git a/block/blk-merge.c b/block/blk-merge.c
>> index 2613531..7b17a65 100644
>> --- a/block/blk-merge.c
>> +++ b/block/blk-merge.c
>> @@ -190,6 +190,7 @@ void blk_queue_split(struct request_queue *q, struct bio **bio,
>>  
>>  bio_chain(split, *bio);
>>  trace_block_split(q, split, (*bio)->bi_iter.bi_sector);
>> +bio_set_flag(*bio, BIO_SPLITED);
>
>Split's past participle form is split, so BIO_SPLIT would be right
>here.


Yea, you are right, it should be BIO_SPLIT


>
>>  generic_make_request(*bio);
>>  *bio = split;
>>  }
>> diff --git a/block/blk-throttle.c b/block/blk-throttle.c
>> index 47a3e54..4ffde95 100644
>> --- a/block/blk-throttle.c
>> +++ b/block/blk-throttle.c
>> @@ -1403,6 +1403,10 @@ bool blk_throtl_bio(struct request_queue *q, struct blkcg_gq *blkg,
>>  
>>  WARN_ON_ONCE(!rcu_read_lock_held());
>>  
>> +/* if the bio has been splited, should not throttle again */
>> +if (bio_flagged(bio, BIO_SPLITED))
>> +goto out;
>> +
>
>But that said, can't we just copy BIO_THROTLED while splitting?


In my opinion, copying BIO_THROTLED while splitting doesn't work
with this, because, the bio within the limit will not set BIO_THROTLED
but will be split, and back to call generic_make_request(), and will be 
count twice.


Thanks,


Jiale


[-- Attachment #2: Type: text/html, Size: 9926 bytes --]

  parent reply	other threads:[~2016-07-06 14:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <77238e99.142c5.155b660564f.Coremail.aaronlee0817@163.com>
2016-07-06  1:10 ` cgroup: Fix split bio been throttled more than once Ming Lei
2016-07-06 14:09   ` Tejun Heo
2016-07-06 14:53     ` Ming Lei
2016-07-07 13:48     ` aaronlee0817
2016-07-08 10:35       ` Ming Lei
2016-07-09 14:53         ` Tejun Heo
2016-07-10  8:58           ` Ming Lei
2016-07-06 14:57   ` aaronlee0817
     [not found] ` <20160705222626.GC25394@htj.duckdns.org>
2016-07-06  1:14   ` Ming Lei
2016-07-06 14:58   ` aaronlee0817 [this message]
2016-07-06 15:06     ` Tejun Heo
2016-07-06 15:17       ` aaronlee0817
2016-07-06 15:39       ` Ming Lei

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=458d1946.12fa6.155c0b80d60.Coremail.aaronlee0817@163.com \
    --to=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=tj@kernel.org \
    --cc=yanzi.zhang@samsung.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