From: Michael Lyle <mlyle@lyle.org>
To: Coly Li <i@coly.li>
Cc: Hannes Reinecke <hare@suse.de>,
Junhui Tang <tang.junhui@zte.com.cn>,
linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: [PATCH 4/5] bcache: writeback: collapse contiguous IO better
Date: Fri, 6 Oct 2017 11:36:36 -0700 [thread overview]
Message-ID: <CAJ+L6qdnzocZRvcExwFBJPmVJnHWNJXY8j3NioUaekAp06QzXg@mail.gmail.com> (raw)
In-Reply-To: <33e52793-251d-ed58-fb59-5432946efb56@coly.li>
Sorry I missed this question:
> Is it the time from writeback starts to dirty reaches dirty target, or
> the time from writeback starts to dirty reaches 0 ?
Not quite either. I monitor the machine with zabbix; it's the time to
when the backing disk reaches its background rate of activity / when
writeback hits its minimum rate (writeback with the PI controller
writes a little past the target because of the integral term).
Viewed one way: 5/80 is just a few percent of difference (6%). But:
I'm hopeful that further improvement can be made along this patch
series, and in any event it's 5 minutes earlier that I/O will have an
unencumbered response time after a pulse of load.
Mike
next prev parent reply other threads:[~2017-10-06 18:36 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 7:32 [PATCH 4/5] bcache: writeback: collapse contiguous IO better tang.junhui
2017-09-27 7:47 ` Michael Lyle
2017-09-27 7:58 ` Michael Lyle
2017-09-30 2:25 ` Coly Li
2017-09-30 3:17 ` Michael Lyle
2017-09-30 6:58 ` Coly Li
2017-09-30 7:13 ` Michael Lyle
2017-09-30 7:13 ` Michael Lyle
2017-09-30 7:33 ` Michael Lyle
2017-09-30 7:33 ` Michael Lyle
2017-09-30 8:03 ` Coly Li
2017-09-30 8:23 ` Michael Lyle
2017-09-30 8:31 ` Michael Lyle
[not found] ` <CAJ+L6qcU+Db5TP1Q2J-V8angdzeW9DFGwc7KQqc4di9CSxusLg@mail.gmail.com>
[not found] ` <CAJ+L6qdu4OSRh7Qdkk-5XBgd4W_N29Y6-wVLf-jFAMKEhQrTbQ@mail.gmail.com>
[not found] ` <CAJ+L6qcyq-E4MrWNfB9kGA8DMD_U1HMxJii-=-qPfv0LeRL45w@mail.gmail.com>
2017-09-30 22:49 ` Michael Lyle
2017-10-01 4:51 ` Coly Li
2017-10-01 16:56 ` Michael Lyle
2017-10-01 16:56 ` Michael Lyle
2017-10-01 17:23 ` Coly Li
2017-10-01 17:34 ` Michael Lyle
2017-10-04 18:43 ` Coly Li
2017-10-04 18:43 ` Coly Li
2017-10-04 23:54 ` Michael Lyle
2017-10-04 23:54 ` Michael Lyle
2017-10-05 17:38 ` Coly Li
2017-10-05 17:53 ` Michael Lyle
2017-10-05 18:07 ` Coly Li
2017-10-05 22:59 ` Michael Lyle
2017-10-06 8:27 ` Coly Li
2017-10-06 9:20 ` Michael Lyle
2017-10-06 10:36 ` Coly Li
2017-10-06 10:42 ` Michael Lyle
2017-10-06 10:42 ` Michael Lyle
2017-10-06 10:56 ` Michael Lyle
2017-10-06 10:56 ` Michael Lyle
2017-10-06 11:00 ` Hannes Reinecke
2017-10-06 11:09 ` Michael Lyle
2017-10-06 11:09 ` Michael Lyle
2017-10-06 11:57 ` Michael Lyle
2017-10-06 11:57 ` Michael Lyle
2017-10-06 12:37 ` Coly Li
2017-10-06 17:36 ` Michael Lyle
2017-10-06 18:09 ` Coly Li
2017-10-06 18:23 ` Michael Lyle
2017-10-06 18:36 ` Michael Lyle [this message]
2017-10-09 18:58 ` Coly Li
2017-10-10 0:00 ` Michael Lyle
2017-10-09 5:59 ` Hannes Reinecke
2017-10-06 12:20 ` Coly Li
2017-10-06 17:53 ` Michael Lyle
-- strict thread matches above, loose matches on Subject: below --
2017-09-29 3:37 tang.junhui
2017-09-29 4:15 ` Michael Lyle
2017-09-29 4:22 ` Coly Li
2017-09-29 4:27 ` Michael Lyle
2017-09-29 4:26 ` Michael Lyle
2017-09-26 19:24 [PATCH 1/5] bcache: don't write back data if reading it failed Michael Lyle
2017-09-26 19:24 ` [PATCH 4/5] bcache: writeback: collapse contiguous IO better Michael Lyle
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=CAJ+L6qdnzocZRvcExwFBJPmVJnHWNJXY8j3NioUaekAp06QzXg@mail.gmail.com \
--to=mlyle@lyle.org \
--cc=hare@suse.de \
--cc=i@coly.li \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=tang.junhui@zte.com.cn \
/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 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.