From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: agk@redhat.com, snitzer@redhat.com
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org,
song@kernel.org, breeves@redhat.com, mpatocka@redhat.com,
khazhy@google.com,
Gabriel Krisman Bertazi <krisman@collabora.com>,
kernel@collabora.com
Subject: [PATCH v4 0/2] Historical Service Time Path Selector
Date: Mon, 11 May 2020 12:39:08 -0400 [thread overview]
Message-ID: <20200511163910.3778467-1-krisman@collabora.com> (raw)
Hi,
This fourth version of HST applies the suggestion from Mikulas Patocka
to do the ktime_get_ns inside the mpath map_bio instead of generic
device-mapper code. This means that struct dm_mpath_io gained another
64bit field. For the request-based case, we continue to use the block
layer start time information.
With this modification, I was able obtain similar performance on BIO
to request-based multipath with HST on the benchmarks shared in v1.
v3: https://www.redhat.com/archives/dm-devel/2020-April/msg00308.html
v2: https://www.redhat.com/archives/dm-devel/2020-April/msg00270.html
v1: https://www.redhat.com/archives/dm-devel/2020-April/msg00176.html
Gabriel Krisman Bertazi (1):
md: mpath: Pass IO start time to path selector
Khazhismel Kumykov (1):
md: mpath: Add Historical Service Time Path Selector
drivers/md/Kconfig | 11 +
drivers/md/Makefile | 1 +
drivers/md/dm-historical-service-time.c | 561 ++++++++++++++++++++++++
drivers/md/dm-mpath.c | 12 +-
drivers/md/dm-path-selector.h | 2 +-
drivers/md/dm-queue-length.c | 2 +-
drivers/md/dm-service-time.c | 2 +-
7 files changed, 585 insertions(+), 6 deletions(-)
create mode 100644 drivers/md/dm-historical-service-time.c
--
2.26.2
next reply other threads:[~2020-05-11 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 16:39 Gabriel Krisman Bertazi [this message]
2020-05-11 16:39 ` [PATCH v4 1/2] md: mpath: Pass IO start time to path selector Gabriel Krisman Bertazi
2020-05-11 16:39 ` [PATCH v4 2/2] md: mpath: Add Historical Service Time Path Selector Gabriel Krisman Bertazi
2020-05-11 17:02 ` [PATCH v4 0/2] " Mike Snitzer
2020-05-11 17:11 ` Gabriel Krisman Bertazi
2020-05-11 17:31 ` Mike Snitzer
2020-05-11 18:41 ` Mike Snitzer
2020-05-11 18:46 ` Gabriel Krisman Bertazi
2020-05-20 23:26 ` [dm-devel] " Xose Vazquez Perez
2020-05-21 0:15 ` Gabriel Krisman Bertazi
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=20200511163910.3778467-1-krisman@collabora.com \
--to=krisman@collabora.com \
--cc=agk@redhat.com \
--cc=breeves@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@redhat.com \
--cc=song@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
all inboxes | Powered by JetHome®