From: lee.tibbert@gmail.com
To: linux-block@vger.kernel.org
Cc: lucmiccio@gmail.com, paolo.valente@linaro.org, lee.tibbert@gmail.com
Subject: Re: [PATCH] block,bfq: Disable writeback throttling
Date: Tue, 3 Oct 2017 12:10:18 -0400 [thread overview]
Message-ID: <20171003161018.18039-1-lee.tibbert@gmail.com> (raw)
In-Reply-To: <20170913100356.3649-1-lucmiccio@gmail.com>
Luca,
Please feel free to add:
Tested-by: Lee Tibbert <lee.tibbert@gmail.com>
The short story is that, with one small commenting issue, the patch is
fine on my system. The small issue is that block/blk-wbt.c line 657 says:
Disable wbt, if enabled by default. Only called from CFQ.
As of this patch, that comment is no longer true. Adding "& BFQ" is
the obvious edit, but simply deleting the "Only" sentence is probably
more robust. IMHO, that should not hold up acceptence of this patch.
Longer story:
In addition to running this for almost three weeks now, I explicitly
tested a number of paths CONFIG_BLK_WBT enabled &
disabled, etc. Details upon request.
In particular, I tested that when CONFIG_BLK_WBT is enabled
sys/block/sda/queue/wbt_lat_usec is cleared when the elevator
is set to BFQ(BFQ-MQ). Patch does what it purports.
I also tested that wbt_lat_usec gets set back to its default when
an elevator other than BFQ is selected after BFQ is active. (Yeah,
the new elevator probably does this. There is no code in BFQ to do it).
This patch makes it easier to get write back settings right when using
cgroups. With cgroup, on wants CONFIG_BLK_DEV_THROTTLING on
but CONFIG_BLK_WBT off. This patch painlessly assures the latter
and reduces, at least my, confusion.
Thank you for this patch. I hope that it is accepted for linux-block in
as time allows.
Lee
next parent reply other threads:[~2017-10-03 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170913100356.3649-1-lucmiccio@gmail.com>
2017-10-03 16:10 ` lee.tibbert [this message]
2017-09-14 7:14 [PATCH] block,bfq: Disable writeback throttling oleksandr
2017-09-19 7:03 ` Paolo Valente
-- strict thread matches above, loose matches on Subject: below --
2017-09-08 9:50 Luca Miccio
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=20171003161018.18039-1-lee.tibbert@gmail.com \
--to=lee.tibbert@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=lucmiccio@gmail.com \
--cc=paolo.valente@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: 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