All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: "Bryn M. Reeves" <bmr@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:03:15 -0400	[thread overview]
Message-ID: <20150819130315.GA24798@redhat.com> (raw)
In-Reply-To: <20150819111122.GE7891@bmr.fab.redhat.com>

On Wed, Aug 19 2015 at  7:11am -0400,
Bryn M. Reeves <bmr@redhat.com> wrote:

> On Wed, Aug 19, 2015 at 06:53:41AM -0400, Mikulas Patocka wrote:
> > On Tue, 18 Aug 2015, Mike Snitzer 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.
> > > 
> > > Userspace will have to check the DM ioctl version to know if DM provides
> > > these extra keywords.
> > > 
> > > Mike
> > 
> > But if you don't send it, userspace will forever have to deal with kernels 
> > that don't report this feature back.
> 
> We'd either end up saying some kernels can't support it when they can, or
> have to carry some additional userspace clutter forever to provide a 
> workaround.

As much as I'd like to push this in the final hour of 4.2's release I'm
sorry that I cannot.  It is too late given it is _not_ a critical fix.

I've bumped the version to .33 and marked this change for stable, just
have lvm2 check for that version in order to support these features.
Yes, it translates to the Linux 4.2.0 release not being supported but
any stable 4.2-stable release will be.

Mike

  reply	other threads:[~2015-08-19 13:03 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
2015-08-19 10:53   ` Mikulas Patocka
2015-08-19 11:11     ` Bryn M. Reeves
2015-08-19 13:03       ` Mike Snitzer [this message]
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=20150819130315.GA24798@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=bmr@redhat.com \
    --cc=breeves@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@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.