lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86eczz3yln.fsf@davidreaver.com>
Date: Sat, 15 Feb 2025 09:29:56 -0800
From: David Reaver <me@...idreaver.com>
To: Konstantin Khlebnikov <koct9i@...il.com>
Cc: Jonathan Corbet <corbet@....net>,  Randy Dunlap <rdunlap@...radead.org>,
  Jens Axboe <axboe@...nel.dk>,  linux-doc@...r.kernel.org,
  linux-block@...r.kernel.org,  linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: iostats: Rewrite intro, remove outdated formats

Konstantin Khlebnikov <koct9i@...il.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ