From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: agk@redhat.com, snitzer@redhat.com, breeves@redhat.com,
linux-kernel@vger.kernel.org, khazhy@google.com, song@kernel.org,
dm-devel@redhat.com, mpatocka@redhat.com, kernel@collabora.com
Subject: Re: [dm-devel] [PATCH v4 0/2] Historical Service Time Path Selector
Date: Wed, 20 May 2020 20:15:09 -0400 [thread overview]
Message-ID: <85tv0am9de.fsf@collabora.com> (raw)
In-Reply-To: <ee987451-6d17-b978-809e-e0fe56dc13ce@gmail.com> (Xose Vazquez Perez's message of "Thu, 21 May 2020 01:26:27 +0200")
Xose Vazquez Perez <xose.vazquez@gmail.com> writes:
> On 5/11/20 6:39 PM, Gabriel Krisman Bertazi wrote:
>
>> 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.
>
> You should add some info to the multipath.conf.5 man page (
> https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=blob;f=multipath/multipath.conf.5;h=05a5e8ffeb110d969f3b2381eb3b88d7f28380f6;hb=HEAD#l189
> ),
> or none one is going to use it.
Sure, will do.
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2020-05-21 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 16:39 [PATCH v4 0/2] Historical Service Time Path Selector Gabriel Krisman Bertazi
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 [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=85tv0am9de.fsf@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 \
--cc=xose.vazquez@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox