From: "Bryn M. Reeves" <bmr@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, Bryn Reeves <breeves@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: dm-statistics: report precise timestamps and histogram
Date: Wed, 19 Aug 2015 11:52:12 +0100 [thread overview]
Message-ID: <20150819105212.GD7891@bmr.fab.redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1508190643410.7633@file01.intranet.prod.int.rdu2.redhat.com>
On Wed, Aug 19, 2015 at 06:50:36AM -0400, Mikulas Patocka wrote:
> On Wed, 19 Aug 2015, Bryn M. Reeves wrote:
> > 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:
> > > > 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
> > >
> > 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.
>
> That's why I think it should be submitted to 4.2 now - so that there won't
> be an upstream kernel without this feature.
Agreed: that's the ideal situation.
Regards,
Bryn.
next prev parent reply other threads:[~2015-08-19 10:52 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
2015-08-19 10:50 ` Mikulas Patocka
2015-08-19 10:52 ` Bryn M. Reeves [this message]
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=20150819105212.GD7891@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).