From: Paolo Valente <paolo.valente@linaro.org> To: Tejun Heo <tj@kernel.org> Cc: Joseph Qi <jiangqi903@gmail.com>, linux-block <linux-block@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>, Shaohua Li <shli@fb.com>, Mark Brown <broonie@kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Ulf Hansson <ulf.hansson@linaro.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: testing io.low limit for blk-throttle Date: Thu, 3 May 2018 18:35:01 +0200 [thread overview] Message-ID: <11A022BD-AAE9-4508-A233-AE05DE33C60A@linaro.org> (raw) In-Reply-To: <20180426183200.GK1911913@devbig577.frc2.facebook.com> > Il giorno 26 apr 2018, alle ore 20:32, Tejun Heo <tj@kernel.org> ha = scritto: >=20 > Hello, >=20 > On Tue, Apr 24, 2018 at 02:12:51PM +0200, Paolo Valente wrote: >> +Tejun (I guess he might be interested in the results below) >=20 > Our experiments didn't work out too well either. At this point, it > isn't clear whether io.low will ever leave experimental state. We're > trying to find a working solution. >=20 Thanks for this update, Tejun. I'm still working (very slowly) on a survey of the current state of affairs in terms of bandwidth and latency guarantees in the block layer. The synthesis of the results I've collected so far is, more or less: "The problem of reaching a high throughput and, at the same time, guaranteeing bandwidth and latency is still unsolved, apart from simple cases, such as homogenous, constant workloads" I'm anticipating this, because I don't want to risk to underestimate anybody's work. So, if anyone has examples of how, e.g., to distribute I/O bandwidth as desired among heterogenous workloads (for instance, random vs sequential workloads) that might fluctuate over time, without losing total throughput, please tell me, and I'll test them. Thanks, Paolo > Thanks. >=20 > --=20 > tejun
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Valente <paolo.valente@linaro.org> To: Tejun Heo <tj@kernel.org> Cc: Joseph Qi <jiangqi903@gmail.com>, linux-block <linux-block@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>, Shaohua Li <shli@fb.com>, Mark Brown <broonie@kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Ulf Hansson <ulf.hansson@linaro.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: testing io.low limit for blk-throttle Date: Thu, 3 May 2018 18:35:01 +0200 [thread overview] Message-ID: <11A022BD-AAE9-4508-A233-AE05DE33C60A@linaro.org> (raw) In-Reply-To: <20180426183200.GK1911913@devbig577.frc2.facebook.com> > Il giorno 26 apr 2018, alle ore 20:32, Tejun Heo <tj@kernel.org> ha scritto: > > Hello, > > On Tue, Apr 24, 2018 at 02:12:51PM +0200, Paolo Valente wrote: >> +Tejun (I guess he might be interested in the results below) > > Our experiments didn't work out too well either. At this point, it > isn't clear whether io.low will ever leave experimental state. We're > trying to find a working solution. > Thanks for this update, Tejun. I'm still working (very slowly) on a survey of the current state of affairs in terms of bandwidth and latency guarantees in the block layer. The synthesis of the results I've collected so far is, more or less: "The problem of reaching a high throughput and, at the same time, guaranteeing bandwidth and latency is still unsolved, apart from simple cases, such as homogenous, constant workloads" I'm anticipating this, because I don't want to risk to underestimate anybody's work. So, if anyone has examples of how, e.g., to distribute I/O bandwidth as desired among heterogenous workloads (for instance, random vs sequential workloads) that might fluctuate over time, without losing total throughput, please tell me, and I'll test them. Thanks, Paolo > Thanks. > > -- > tejun
next prev parent reply other threads:[~2018-05-03 16:35 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-22 9:23 testing io.low limit for blk-throttle Paolo Valente 2018-04-22 13:29 ` jianchao.wang 2018-04-22 15:53 ` Paolo Valente 2018-04-23 2:19 ` jianchao.wang 2018-04-23 5:32 ` Paolo Valente 2018-04-23 6:35 ` jianchao.wang 2018-04-23 7:37 ` Paolo Valente 2018-04-23 8:26 ` jianchao.wang 2018-04-23 6:05 ` Joseph Qi 2018-04-23 7:35 ` Paolo Valente 2018-04-23 9:01 ` Joseph Qi 2018-04-24 12:12 ` Paolo Valente 2018-04-24 12:12 ` Paolo Valente 2018-04-25 12:13 ` Joseph Qi 2018-04-26 17:27 ` Paolo Valente 2018-04-27 3:27 ` Joseph Qi 2018-04-27 5:14 ` Paolo Valente 2018-04-27 5:14 ` Paolo Valente 2018-04-26 18:32 ` Tejun Heo 2018-04-27 2:09 ` jianchao.wang 2018-04-27 2:40 ` Joseph Qi 2018-05-03 16:35 ` Paolo Valente [this message] 2018-05-03 16:35 ` Paolo Valente
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=11A022BD-AAE9-4508-A233-AE05DE33C60A@linaro.org \ --to=paolo.valente@linaro.org \ --cc=axboe@kernel.dk \ --cc=broonie@kernel.org \ --cc=jiangqi903@gmail.com \ --cc=linus.walleij@linaro.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=shli@fb.com \ --cc=tj@kernel.org \ --cc=ulf.hansson@linaro.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.