From: Jens Axboe <axboe@kernel.dk>
To: Tejun Heo <tj@kernel.org>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, cgroups@vger.kernel.org
Subject: Re: [PATCH 1/3 for-5.4/block] iocost: better trace vrate changes
Date: Thu, 26 Sep 2019 09:12:38 +0200 [thread overview]
Message-ID: <310739da-b606-6485-9979-9bc03a592265@kernel.dk> (raw)
In-Reply-To: <20190925230207.GI2233839@devbig004.ftw2.facebook.com>
On 9/26/19 1:02 AM, Tejun Heo wrote:
> vrate_adj tracepoint traces vrate changes; however, it does so only
> when busy_level is non-zero. busy_level turning to zero can sometimes
> be as interesting an event. This patch also enables vrate_adj
> tracepoint on other vrate related events - busy_level changes and
> non-zero nr_lagging.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> Hello, Jens.
>
> I've encountered vrate regulation issues while testing on a hard disk
> machine. These are three patches to improve vrate adj visibility and
> fix the issue.
Applied 1-3 for 5.4, thanks Tejun.
--
Jens Axboe
prev parent reply other threads:[~2019-09-26 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 23:02 [PATCH 1/3 for-5.4/block] iocost: better trace vrate changes Tejun Heo
2019-09-25 23:03 ` [PATCH 2/3 for-5.4/block] iocost: improve nr_lagging handling Tejun Heo
2019-09-25 23:03 ` [PATCH 3/3 for-5.4/block] iocost: bump up default latency targets for hard disks Tejun Heo
2019-09-26 7:12 ` Jens Axboe [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=310739da-b606-6485-9979-9bc03a592265@kernel.dk \
--to=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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