All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	andrii.anisov@gmail.com, Julien Grall <julien.grall@arm.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	"andrii_anisov@epam.com" <andrii_anisov@epam.com>
Subject: Re: [PATCH] perfc: Print a system time in a convenient format
Date: Tue, 11 Sep 2018 10:51:02 +0100	[thread overview]
Message-ID: <59c69d1a-f8ae-3cf8-3227-c89bdf116383@citrix.com> (raw)
In-Reply-To: <5B978BF202000078001E71A3@prv1-mh.provo.novell.com>

On 09/11/2018 10:33 AM, Jan Beulich wrote:
>>>> On 11.09.18 at 11:24, <george.dunlap@citrix.com> wrote:
>> On 09/11/2018 09:50 AM, Andrii Anisov wrote:
>>> Hello Jan,
>>>
>>>
>>> On 11.09.18 11:27, Jan Beulich wrote:
>>>> NAK, for two reasons: I'm not of the opinion that reading a 15 or more
>>>> digit decimal number without any separators is any easier than the
>>>> current format.
>>> It's quite subjective. IMHO timestamps measured in ns easier to
>>> understand in decimals rather than in separated 32-bit hex-es. No matter
>>> how many digital number they have.
>>> Even post processing of perfc output is easier in case of decimal
>>> timestamps. You should not parse hexes and odd separators to calculate
>>> the time elapsed between two samples.
>>
>> I agree with this.  Printing in hexadecimal is useful if you need to see
>> the bitwise structure of the content; that's of zero use when it comes
>> to timestamps.  On the contrary, you almost always want to be able to do
>> a subtraction in your head and get at least an order-of-magnitude
>> difference between the times, something which is far too difficult in hex.
> 
> I disagree - it's a matter of who looks at those numbers. Personally
> I'm quite fine doing order-of-magnitude hex math.

So quick, about how long is 0x10:00000000 ns?

Maybe you know how long that is, but I would posit that if so, you are
among a handful of people worldwide who have happened to train yourself
in that knowledge.  The millions of Xen developers and system
administrators worldwide who don't have that sense, and (like me) have
absolutely no interest in gaining that knowledge.  I have much better
things to do with my time.

Changing it to seconds (i.e., using the decimal point as a "separator")
would make sense, and I'd be in favor of a patch which did something to
that effect.  But PRI_stime is still an improvement (for the vast
majority of our users and developers); we shouldn't let the best become
the enemy of the good.

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2018-09-11  9:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  6:53 [PATCH] perfc: Print a system time in a convenient format Andrii Anisov
2018-09-11  8:27 ` Jan Beulich
2018-09-11  8:50   ` Andrii Anisov
2018-09-11  9:10     ` Jan Beulich
2018-09-11  9:15       ` Andrew Cooper
2018-09-11  9:18         ` Jan Beulich
2018-09-11  9:20           ` Andrew Cooper
2018-09-11  9:28             ` Jan Beulich
2018-09-11  9:21           ` Andrii Anisov
2018-09-11  9:30             ` Jan Beulich
2018-09-11  9:49               ` Andrii Anisov
2018-09-11 14:04                 ` Andrii Anisov
2018-09-11 14:27                   ` George Dunlap
2018-09-11 14:33                   ` Jan Beulich
2018-09-11  9:28           ` George Dunlap
2018-09-11  9:37             ` Jan Beulich
2018-09-11  9:19       ` Andrii Anisov
2018-09-11  9:24     ` George Dunlap
2018-09-11  9:33       ` Jan Beulich
2018-09-11  9:50         ` Andrii Anisov
2018-09-11  9:51         ` George Dunlap [this message]

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=59c69d1a-f8ae-3cf8-3227-c89bdf116383@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=andrii.anisov@gmail.com \
    --cc=andrii_anisov@epam.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.