From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: testing io.low limit for blk-throttle To: Paolo Valente Cc: linux-block , Jens Axboe , Shaohua Li , Mark Brown , Linus Walleij , Ulf Hansson References: <180654d2-17ef-0d25-bef6-f526e9ec4ea3@oracle.com> <0AAB1A24-0E2E-4054-8D7F-6C1D69379A1F@linaro.org> <94F005D5-EC8B-4830-AD5B-489117F7DC60@linaro.org> From: "jianchao.wang" Message-ID: <5921aa86-37d9-a85d-18da-ff363ff83cf2@oracle.com> Date: Mon, 23 Apr 2018 14:35:04 +0800 MIME-Version: 1.0 In-Reply-To: <94F005D5-EC8B-4830-AD5B-489117F7DC60@linaro.org> Content-Type: text/plain; charset=utf-8 List-ID: Hi Paolo On 04/23/2018 01:32 PM, Paolo Valente wrote: > Thanks for sharing this fix. I tried it too, but nothing changes in > my test :(> That's really sad. > At this point, my doubt is still: am I getting io.low limit right? I > understand that an I/O-bound group should be guaranteed a rbps at > least equal to the rbps set with io.low for that group (of course, > provided that the sum of io.low limits is lower than the rate at which > the device serves all the I/O generated by the groups). Is this > really what io.low shall guarantee? I agree with your point about this even if I'm not qualified to judge it. On the other hand, could you share your test case and blk-throl config here ? Thanks Jianchao