From: Paolo Valente <paolo.valente@linaro.org>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
ksummit-discuss@lists.linux-foundation.org,
Jens Axboe <axboe@fb.com>,
hare@suse.de, Tejun Heo <tj@kernel.org>,
osandov@osandov.com, hch@lst.de
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Addressing long-standing high-latency problems related to I/O
Date: Wed, 21 Sep 2016 16:37:53 +0200 [thread overview]
Message-ID: <8953DCE7-F18B-4A31-BC05-6483204E2863@linaro.org> (raw)
In-Reply-To: <8adc094c-bf02-ecc3-67ac-7ffac3ef2491@sandisk.com>
> Il giorno 21 set 2016, alle ore 16:30, Bart Van Assche <bart.vanassche@sandisk.com> ha scritto:
>
> On 09/16/16 00:55, Paolo Valente wrote:
>> Linux systems suffers from long-standing high-latency problems, at
>> system and application level, related to I/O.
>
> Hello Paolo,
>
Hi
> Are you aware of Jens' throttled background buffered writeback work? If not, can you repeat your measurements against a kernel on which these patches have been applied?
Already done (see below).
> See also http://www.spinics.net/lists/linux-fsdevel/msg101391.html.
>
A brief report of the outcome of my measurements is in this email of mine on the same thread:
http://www.spinics.net/lists/linux-fsdevel/msg101430.html
In short, application start-up time happened to be about the same with and without writeback throttling (actually slightly higher with throttling, for, e.g., gnome-terminal).
Thanks,
Paolo
> Thanks,
>
> Bart.
>
prev parent reply other threads:[~2016-09-21 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 7:55 Paolo Valente
2016-09-16 8:24 ` Greg KH
2016-09-16 8:59 ` Linus Walleij
2016-09-16 9:10 ` Bart Van Assche
2016-09-16 11:24 ` Linus Walleij
2016-09-16 11:46 ` Arnd Bergmann
2016-09-16 13:10 ` Paolo Valente
2016-09-16 13:36 ` Linus Walleij
2016-09-16 11:53 ` Bart Van Assche
2016-09-22 9:18 ` Ulf Hansson
2016-09-22 11:06 ` Linus Walleij
2016-09-16 15:15 ` James Bottomley
2016-09-16 18:48 ` Paolo Valente
2016-09-16 19:36 ` James Bottomley
2016-09-16 20:13 ` Paolo Valente
2016-09-19 8:17 ` Jan Kara
2016-09-17 10:31 ` Linus Walleij
2016-09-21 13:51 ` Grant Likely
2016-09-21 14:30 ` Bart Van Assche
2016-09-21 14:37 ` Paolo Valente [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=8953DCE7-F18B-4A31-BC05-6483204E2863@linaro.org \
--to=paolo.valente@linaro.org \
--cc=axboe@fb.com \
--cc=b.zolnierkie@samsung.com \
--cc=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=osandov@osandov.com \
--cc=tj@kernel.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: 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