qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
	qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [PATCH] block/nvme: Add driver statistics for access alignment and hw errors
Date: Thu, 1 Oct 2020 12:29:18 +0200	[thread overview]
Message-ID: <42fc436d-bb93-d784-a0f5-6b2dccb6419c@redhat.com> (raw)
In-Reply-To: <20201001095903.GA343239@stefanha-x1.localdomain>

On 10/1/20 11:59 AM, Stefan Hajnoczi wrote:
> On Wed, Sep 30, 2020 at 03:36:17PM +0200, Philippe Mathieu-Daudé wrote:
>>     "return": [
>>         {
>>             "device": "",
>>             "node-name": "drive0",
>>             "stats": {
>>                 "flush_total_time_ns": 6026948,
>>                 "wr_highest_offset": 3383991230464,
>>                 "wr_total_time_ns": 807450995,
>>                 "failed_wr_operations": 0,
>>                 "failed_rd_operations": 0,
>>                 "wr_merged": 3,
>>                 "wr_bytes": 50133504,
>>                 "failed_unmap_operations": 0,
>>                 "failed_flush_operations": 0,
>>                 "account_invalid": false,
>>                 "rd_total_time_ns": 1846979900,
>>                 "flush_operations": 130,
>>                 "wr_operations": 659,
>>                 "rd_merged": 1192,
>>                 "rd_bytes": 218244096,
>>                 "account_failed": false,
>>                 "idle_time_ns": 2678641497,
>>                 "rd_operations": 7406,
>>             },
>>             "driver-specific": {
>>                 "driver": "nvme",
>>                 "completion-errors": 0,
>>                 "unaligned-access-nb": 2959,
>>                 "aligned-access-nb": 4477
> 
> "nb" is number?

Yes:

 # @aligned-access-nb: The number of aligned accesses performed by
 #                     the driver.
 #
 # @unaligned-access-nb: The number of unaligned accesses performed by
 #                       the driver.

Copied from:

qapi/block-core.json:928:# @discard-nb-ok: The number of successful
discard operations performed by
qapi/block-core.json:931:# @discard-nb-failed: The number of failed
discard operations performed by
qapi/block-core.json:940:      'discard-nb-ok': 'uint64',
qapi/block-core.json:941:      'discard-nb-failed': 'uint64',

> 
> Using plural ("unaligned-accesses" and "aligned-accesses") makes it
> clear that the value is a count. It's also consistent with the existing
> "wr_operations" and "failed_operations" stats.

OK, I'll update.

Thanks for the review,

Phil.




      reply	other threads:[~2020-10-01 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 13:36 [PATCH] block/nvme: Add driver statistics for access alignment and hw errors Philippe Mathieu-Daudé
2020-10-01  9:59 ` Stefan Hajnoczi
2020-10-01 10:29   ` Philippe Mathieu-Daudé [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=42fc436d-bb93-d784-a0f5-6b2dccb6419c@redhat.com \
    --to=philmd@redhat.com \
    --cc=armbru@redhat.com \
    --cc=fam@euphon.net \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@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).