From: Jens Axboe <axboe@kernel.dk>
To: vincent.fu@samsung.com, fio@vger.kernel.org
Subject: Re: [PATCH 0/5] Latency cleanups
Date: Wed, 15 Jun 2022 15:30:37 -0600 [thread overview]
Message-ID: <165532863709.858685.15018475756909381631.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220614155822.307771-1-vincent.fu@samsung.com>
On Tue, 14 Jun 2022 15:58:29 +0000, Vincent Fu wrote:
> Jens, here are a few latency cleanup patches. The main improvement is to
> avoid recording issue_time twice for the ioengines that record
> issue_time themselves when their commit hook is called. Recording
> issue_time twice underestimates clat since the first issue_time value is
> used for slat and then the later second issue_time is used when
> calculating clat.
>
> [...]
Applied, thanks!
[1/5] ioengines: add helper for trims with async ioengines
commit: d46b4565dfdaddbfdd91976a57b2564aa7a52f62
[2/5] ioengines: don't record issue_time if ioengines already do it
commit: 4e7e78980ff32627e12b48d72496b701dd200a42
[3/5] HOWTO: improve description of latency measures
commit: 13ddd98b2a70c55657f952096785ccc64479f0eb
[4/5] ioengines: update last_issue if we set issue_time
commit: 39f56400f63e43fbe33e391d52f24eb6c79d0098
[5/5] ioengines: clean up latency accounting for 3 ioengines
commit: 2b82135e42fc5872338ee16e16d317b16abfe308
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-15 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220614155830uscas1p1e1d6595b29fb6960b405d5b295a32ffc@uscas1p1.samsung.com>
2022-06-14 15:58 ` [PATCH 0/5] Latency cleanups Vincent Fu
[not found] ` <CGME20220614155830uscas1p15aaa5d3bc8eec3da42c78a48520c6dd9@uscas1p1.samsung.com>
2022-06-14 15:58 ` [PATCH 2/5] ioengines: don't record issue_time if ioengines already do it Vincent Fu
2022-06-15 15:26 ` Nick Neumann
2022-06-15 17:06 ` Vincent Fu
2022-06-15 17:51 ` Nick Neumann
[not found] ` <CGME20220614155831uscas1p2312cb623924e5df60abefb210affa1f4@uscas1p2.samsung.com>
2022-06-14 15:58 ` [PATCH 3/5] HOWTO: improve description of latency measures Vincent Fu
[not found] ` <CGME20220614155831uscas1p12c7b262538a47a417dc783a45e8df049@uscas1p1.samsung.com>
2022-06-14 15:58 ` [PATCH 4/5] ioengines: update last_issue if we set issue_time Vincent Fu
[not found] ` <CGME20220614155830uscas1p2586c5e612430bdd2ce455a1081ce08e4@uscas1p2.samsung.com>
2022-06-14 15:58 ` [PATCH 1/5] ioengines: add helper for trims with async ioengines Vincent Fu
[not found] ` <CGME20220614155831uscas1p16ab7450c13a1587f2058617130f4f122@uscas1p1.samsung.com>
2022-06-14 15:58 ` [PATCH 5/5] ioengines: clean up latency accounting for 3 ioengines Vincent Fu
2022-06-15 21:30 ` 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=165532863709.858685.15018475756909381631.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=vincent.fu@samsung.com \
/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.