linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <yang.yang29@zte.com.cn>
To: <bagasdotme@gmail.com>
Cc: <akpm@linux-foundation.org>, <david@redhat.com>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<linux-doc@vger.kernel.org>, <wang.yong12@zte.com.cn>
Subject: Re: [PATCH linux-next] delayacct: improve the average delay precision of getdelay tool to microsecond
Date: Thu, 2 Mar 2023 11:26:35 +0800 (CST)	[thread overview]
Message-ID: <202303021126356602083@zte.com.cn> (raw)
In-Reply-To: <ZAAOa4nYSYQc48Lr@debian.me>

> I'm kinda confused. 0.000ms is same as 0ms, right?
Not really. The types of these two results are different, so the precision of
representation is different.

> And did you mean accuracy of delay average is to be same as CPU time?
Yes.


      reply	other threads:[~2023-03-02  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  6:08 yang.yang29
2023-03-02  2:48 ` Bagas Sanjaya
2023-03-02  3:26   ` yang.yang29 [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=202303021126356602083@zte.com.cn \
    --to=yang.yang29@zte.com.cn \
    --cc=akpm@linux-foundation.org \
    --cc=bagasdotme@gmail.com \
    --cc=david@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wang.yong12@zte.com.cn \
    /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