public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: David Reaver <me@davidreaver.com>
To: Konstantin Khlebnikov <koct9i@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	 Randy Dunlap <rdunlap@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	 linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: iostats: Rewrite intro, remove outdated formats
Date: Sat, 15 Feb 2025 09:29:56 -0800	[thread overview]
Message-ID: <86eczz3yln.fsf@davidreaver.com> (raw)
In-Reply-To: <CALYGNiOA4K4PQcJTk_OwkHOamW-Am_gKSUZoog41v+Y_+qEQxg@mail.gmail.com> (Konstantin Khlebnikov's message of "Sat, 15 Feb 2025 18:18:20 +0100")

Konstantin Khlebnikov <koct9i@gmail.com> writes:

> There is another case when counters back to zero:
> device reattachment or reinitialization.
> The device itself might be the same or completely different,
> but statistics sampling will see only restart from zero.
>
> So, maybe rephrase that counters sometimes restarts at zero.
> For example at boot, device attachment, or counter overflows.

That makes sense. How does this version of that paragraph sound?

  All fields are cumulative, monotonic counters, except for field 9, which
  resets to zero as I/Os complete. The remaining fields reset at boot, on
  device reattachment or reinitialization, or when the underlying counter
  overflows. Applications reading these counters should detect and handle
  resets when comparing stat snapshots.

Thanks for your feedback!

Thanks,
David Reaver

  reply	other threads:[~2025-02-15 17:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14  1:39 [PATCH] docs: iostats: Update introduction with flush fields David Reaver
2025-02-14  2:21 ` Randy Dunlap
2025-02-14  5:14   ` [PATCH] docs: iostats: Rewrite intro, remove outdated formats David Reaver
2025-02-14 10:21     ` Bagas Sanjaya
2025-02-14 15:48     ` Jonathan Corbet
2025-02-14 15:56       ` David Reaver
     [not found]     ` <CALYGNiOU3vPAyvsNv4rt=qZRbZFVZ9iAe+kzPzGKkx6_L3wG5Q@mail.gmail.com>
2025-02-14 17:39       ` David Reaver
2025-02-15 17:18         ` Konstantin Khlebnikov
2025-02-15 17:29           ` David Reaver [this message]
2025-02-15 17:46             ` Konstantin Khlebnikov

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=86eczz3yln.fsf@davidreaver.com \
    --to=me@davidreaver.com \
    --cc=axboe@kernel.dk \
    --cc=corbet@lwn.net \
    --cc=koct9i@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox