From: "Bryn M. Reeves" <bmr@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, Bryn Reeves <breeves@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: dm-statistics: report precise timestamps and histogram
Date: Wed, 19 Aug 2015 09:48:28 +0100 [thread overview]
Message-ID: <20150819084828.GB7891@bmr.fab.redhat.com> (raw)
In-Reply-To: <20150818214112.GA17757@redhat.com>
On Tue, Aug 18, 2015 at 05:41:12PM -0400, Mike Snitzer wrote:
> On Tue, Aug 18 2015 at 5:07pm -0400,
> Mike Snitzer <snitzer@redhat.com> wrote:
>
> > On Tue, Aug 18 2015 at 4:26pm -0400,
> > Mikulas Patocka <mpatocka@redhat.com> wrote:
> >
> > > Mike, please submit this patch to the upstream kernel before 4.2 is
> > > released, so that the all the kernels that support the options
> > > "precise_timestamps" and "histogram" also report these values back.
> >
> > It is really late to be sending pull requests for 4.2 (next release is
> > likely 4.2 final). I've already sent 6 'fixes' pull requests to Linus
> > for 4.2. This patch is just too late, sorry.
> >
> > But what I will do is tag this commit for 4.2-stable inclusion.
> >
> > Userspace will have to check the DM ioctl version to know if DM provides
> > these extra keywords.
>
> I've staged the following for 4.3:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=bd49784fd1e8f42c7600fbfa206361324857f373
>
> Bryn, please verify this change is sufficient for your needs.
Yes; this will be usable by dmstats.
Unfortuntely the fact that there are kernels out there without this
means that we will need to either carry a workaround in dmstats
userspace forever or just disallow use of these features on those
kernels.
The workaround is fairly unobtrusive and is already written so it's not
the end of the world (it also has future uses for which kernel support
will not help so it won't be solely used for precise/histogram
tracking).
Regards,
Bryn.
next prev parent reply other threads:[~2015-08-19 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 20:26 [PATCH] dm-statistics: report precise timestamps and histogram Mikulas Patocka
2015-08-18 21:07 ` Mike Snitzer
2015-08-18 21:41 ` Mike Snitzer
2015-08-19 8:48 ` Bryn M. Reeves [this message]
2015-08-19 10:50 ` Mikulas Patocka
2015-08-19 10:52 ` Bryn M. Reeves
2015-08-19 10:53 ` Mikulas Patocka
2015-08-19 11:11 ` Bryn M. Reeves
2015-08-19 13:03 ` Mike Snitzer
2015-08-20 19:40 ` Mikulas Patocka
2015-08-21 7:58 ` Bryn M. Reeves
2015-08-19 8:43 ` [PATCH] " Bryn M. Reeves
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=20150819084828.GB7891@bmr.fab.redhat.com \
--to=bmr@redhat.com \
--cc=agk@redhat.com \
--cc=breeves@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.com \
--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 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.