public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Gabriel Krisman Bertazi <krisman@collabora.com>,
	agk@redhat.com, snitzer@redhat.com
Cc: 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: Thu, 21 May 2020 01:26:27 +0200	[thread overview]
Message-ID: <ee987451-6d17-b978-809e-e0fe56dc13ce@gmail.com> (raw)
In-Reply-To: <20200511163910.3778467-1-krisman@collabora.com>

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.


Thanks.

  parent reply	other threads:[~2020-05-20 23:26 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 ` Xose Vazquez Perez [this message]
2020-05-21  0:15   ` [dm-devel] " 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=ee987451-6d17-b978-809e-e0fe56dc13ce@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=agk@redhat.com \
    --cc=breeves@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=kernel@collabora.com \
    --cc=khazhy@google.com \
    --cc=krisman@collabora.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