From: Jens Axboe <axboe@kernel.dk>
To: Gulam Mohamed <gulam.mohamed@oracle.com>, linux-block@vger.kernel.org
Cc: philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
christoph.boehmwalder@linbit.com, minchan@kernel.org,
ngupta@vflare.org, senozhatsky@chromium.org, colyli@suse.de,
kent.overstreet@gmail.com, agk@redhat.com, snitzer@kernel.org,
dm-devel@redhat.com, song@kernel.org, dan.j.williams@intel.com,
vishal.l.verma@intel.com, dave.jiang@intel.com,
ira.weiny@intel.com, junxiao.bi@oracle.com,
martin.petersen@oracle.com, kch@nvidia.com,
drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org,
linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org,
nvdimm@lists.linux.dev, konrad.wilk@oracle.com
Subject: Re: [RFC] block: Change the granularity of io ticks from ms to ns
Date: Wed, 7 Dec 2022 10:08:50 -0700 [thread overview]
Message-ID: <eaf4f9a8-dfc6-402e-4a1a-732034d1512d@kernel.dk> (raw)
In-Reply-To: <20221206181536.13333-1-gulam.mohamed@oracle.com>
On 12/6/22 11:15?AM, Gulam Mohamed wrote:
> Use ktime to change the granularity of IO accounting in block layer from
> milli-seconds to nano-seconds to get the proper latency values for the
> devices whose latency is in micro-seconds. After changing the granularity
> to nano-seconds the iostat command, which was showing incorrect values for
> %util, is now showing correct values.
>
> We did not work on the patch to drop the logic for
> STAT_PRECISE_TIMESTAMPS yet. Will do it if this patch is ok.
>
> The iostat command was run after starting the fio with following command
> on an NVME disk. For the same fio command, the iostat %util was showing
> ~100% for the disks whose latencies are in the range of microseconds.
> With the kernel changes (granularity to nano-seconds), the %util was
> showing correct values. Following are the details of the test and their
> output:
As mentioned, this will most likely have a substantial performance
impact. I'd test it, but your patch is nowhere near applying to the
current block tree. Please resend it against for-6.2/block so it can
get tested.
--
Jens Axboe
prev parent reply other threads:[~2022-12-07 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 18:15 [RFC] block: Change the granularity of io ticks from ms to ns Gulam Mohamed
2022-12-06 19:31 ` Paul Menzel
2022-12-07 2:19 ` Yu Kuai
2022-12-07 3:15 ` Ming Lei
2022-12-07 13:09 ` Yu Kuai
2022-12-07 17:22 ` Jens Axboe
2022-12-07 17:08 ` Jens Axboe [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=eaf4f9a8-dfc6-402e-4a1a-732034d1512d@kernel.dk \
--to=axboe@kernel.dk \
--cc=agk@redhat.com \
--cc=christoph.boehmwalder@linbit.com \
--cc=colyli@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dm-devel@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=gulam.mohamed@oracle.com \
--cc=ira.weiny@intel.com \
--cc=junxiao.bi@oracle.com \
--cc=kch@nvidia.com \
--cc=kent.overstreet@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=nvdimm@lists.linux.dev \
--cc=philipp.reisner@linbit.com \
--cc=senozhatsky@chromium.org \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=vishal.l.verma@intel.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).