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: Re: cgroup: Fix split bio been throttled more than once
Date: Wed, 6 Jul 2016 23:17:12 +0800 (CST) [thread overview]
Message-ID: <47bdfb31.1320b.155c0c8ca34.Coremail.aaronlee0817@163.com> (raw)
In-Reply-To: <20160706150629.GA31684@mtj.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
>At 2016-07-06 23:06:29, "Tejun Heo" <tj@kernel.org> wrote:
>Hello,
>
>On Wed, Jul 06, 2016 at 10:58:55PM +0800, aaronlee0817 wrote:
>> >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.
>
>I see. It's just a bit weird that we're marking this from clone site
>when it's an issue which is specific to throttling. The thing is
>depending on how bio clone is used, it could misbehave in the other
>direction (bio not accounted at all). What we want to know is whether
>a bio has been previously accounted or not, rather than whether a bio
>is a result of splitting. I think it'd be better to track that
>instead.
Yea, I agree with you, we should consider this more carefully, I will
check more about what you mentioned and to see if we have better
way to fix this.
>
>Thanks.
>
>--
>tejun
Thanks,
Jiale
[-- Attachment #2: Type: text/html, Size: 1437 bytes --]
next prev parent reply other threads:[~2016-07-06 15:17 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
2016-07-06 15:06 ` Tejun Heo
2016-07-06 15:17 ` aaronlee0817 [this message]
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=47bdfb31.1320b.155c0c8ca34.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