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, song@kernel.org,
breeves@redhat.com, mpatocka@redhat.com, khazhy@google.com,
kernel@collabora.com
Subject: Re: [PATCH v4 0/2] Historical Service Time Path Selector
Date: Mon, 11 May 2020 14:46:21 -0400 [thread overview]
Message-ID: <85blmul37m.fsf@collabora.com> (raw)
In-Reply-To: <20200511184143.GA8274@redhat.com> (Mike Snitzer's message of "Mon, 11 May 2020 14:41:43 -0400")
Mike Snitzer <snitzer@redhat.com> writes:
> OK, that concall's issue had nothing to do with needing higher
> resolution time (was about IOPs realized with requested-based vs
> bio-based).
>
> Reality is, DM won't need anything higher resolution than jiffies until
> block core's interfaces require something other than jiffies
> (e.g. generic_end_io_acct).
>
> So feel free to proceed with the conditional time fetch solution you
> were going to run with (prior to my previous mail asking you to hold
> off).
>
> Sorry for the noise. Thanks,
> Mike
No problem, thanks for the information. I get started on it.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2020-05-11 18:46 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 [this message]
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=85blmul37m.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 \
/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.