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: Fri, 21 Aug 2015 08:58:08 +0100 [thread overview]
Message-ID: <20150821075807.GA30108@bmr.fab.redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1508201538560.24681@file01.intranet.prod.int.rdu2.redhat.com>
On Thu, Aug 20, 2015 at 03:40:10PM -0400, Mikulas Patocka wrote:
>
>
> On Wed, 19 Aug 2015, Bryn M. Reeves 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.
> >
> > Regards,
> > Bryn.
>
> I think you don't need to provide a workaround for kernels that don't
> report it. The workaround would be needed just for 4.2.0 (Mike said he
> will backport the fix to 4.2.1), there is no need to bloat userspace with
> that.
That's what's been done; the aux data stuff has been stripped out & I've
set the ioctl version check at 4.33.0.
Bryn.
next prev parent reply other threads:[~2015-08-21 7:58 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
2015-08-20 19:40 ` Mikulas Patocka
2015-08-21 7:58 ` Bryn M. Reeves [this message]
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=20150821075807.GA30108@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).