From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: agk@redhat.com, dm-devel@redhat.com,
linux-kernel@vger.kernel.org, khazhy@google.com,
kernel@collabora.com
Subject: Re: [PATCH 0/2] Historical Service Time Path Selector
Date: Sun, 26 Apr 2020 16:00:17 -0400 [thread overview]
Message-ID: <855zdm2f1q.fsf@collabora.com> (raw)
In-Reply-To: <20200423205947.GA13657@lobo> (Mike Snitzer's message of "Thu, 23 Apr 2020 16:59:47 -0400")
Mike Snitzer <snitzer@redhat.com> writes:
>
> Looks like you've put a lot of time to this and I'd be happy to help
> you get this to land upstream.
>
> But... (you knew there'd be at least one "but" right? ;) I'm not
> liking making this path selector request-based specific. All other
> selectors up to this point are request-based vs bio-based agnostic.
>
> Would you be open to dropping patch 1/2 and replacing it with
> something like the following patch?
>
> Then you'd pass 'u64 start_time_ns' into the path_selector_type's
> .end_io (and possibly .start_io).
I think it is fine.
Kind of a MD newbie question, but if I understand correctly,
dm_start_time_ns_from_clone is only for bio based multipath, and we just
pass req->io_start_time directly on request based multipath, right? If
I understand the code correctly, start_io_acct is only called for the
bio level DM.
I will update the patches, do a quick round of tests with BIO based and
send a v2.
Thanks a lot,
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2020-04-26 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 21:13 [PATCH 0/2] Historical Service Time Path Selector Gabriel Krisman Bertazi
2020-04-16 21:13 ` [PATCH 1/2] md: Expose struct request to path selector Gabriel Krisman Bertazi
2020-04-16 21:13 ` [PATCH 2/2] md: Add Historical Service Time Path Selector Gabriel Krisman Bertazi
2020-04-23 20:59 ` [PATCH 0/2] " Mike Snitzer
2020-04-26 20:00 ` 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=855zdm2f1q.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.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