All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 1/2] proc_pid_io.5: stats include children
Date: Sun, 17 Mar 2024 12:39:14 +0100	[thread overview]
Message-ID: <ZfbWaLu0o6towx2W@debian> (raw)
In-Reply-To: <4eb567da5a26a4886478c65ee90fe73d570e291f.1710673156.git.nabijaczleweli@nabijaczleweli.xyz>

[-- Attachment #1: Type: text/plain, Size: 3069 bytes --]

Hi наб!

On Sun, Mar 17, 2024 at 12:01:43PM +0100, наб wrote:

[...]

> Just s/process/& and its waited-for children/ but re-broken per review.
> 
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>

Patch applied.  (And /^Just/d )  Thanks!

Have a lovely day!
Alex

> ---
>  man5/proc_pid_io.5 | 27 ++++++++++++++++++---------
>  1 file changed, 18 insertions(+), 9 deletions(-)
> 
> diff --git a/man5/proc_pid_io.5 b/man5/proc_pid_io.5
> index d6eaebf5d..dc75a91de 100644
> --- a/man5/proc_pid_io.5
> +++ b/man5/proc_pid_io.5
> @@ -11,7 +11,9 @@ .SH DESCRIPTION
>  .TP
>  .IR /proc/ pid /io " (since Linux 2.6.20)"
>  .\" commit 7c3ab7381e79dfc7db14a67c6f4f3285664e1ec2
> -This file contains I/O statistics for the process, for example:
> +This file contains I/O statistics
> +for the process and its waited-for children,
> +for example:
>  .IP
>  .in +4n
>  .EX
> @@ -30,7 +32,9 @@ .SH DESCRIPTION
>  .RS
>  .TP
>  .IR rchar ": characters read"
> -The number of bytes which this task has caused to be read from storage.
> +The number of bytes
> +which this task and its waited-for children
> +have caused to be read from storage.
>  This is simply the sum of bytes which this process passed to
>  .BR read (2)
>  and similar system calls.
> @@ -40,8 +44,9 @@ .SH DESCRIPTION
>  pagecache).
>  .TP
>  .IR wchar ": characters written"
> -The number of bytes which this task has caused, or shall cause to be written
> -to disk.
> +The number of bytes
> +which this task and its waited-for children
> +have caused, or shall cause to be written to disk.
>  Similar caveats apply here as with
>  .IR rchar .
>  .TP
> @@ -60,20 +65,24 @@ .SH DESCRIPTION
>  .BR pwrite (2).
>  .TP
>  .IR read_bytes ": bytes read"
> -Attempt to count the number of bytes which this process really did cause to
> -be fetched from the storage layer.
> +Attempt to count the number of bytes
> +which this process and its waited-for children
> +really did cause to be fetched from the storage layer.
>  This is accurate for block-backed filesystems.
>  .TP
>  .IR write_bytes ": bytes written"
> -Attempt to count the number of bytes which this process caused to be sent to
> -the storage layer.
> +Attempt to count the number of bytes
> +which this process and its waited-for children
> +caused to be sent to the storage layer.
>  .TP
>  .IR cancelled_write_bytes :
>  The big inaccuracy here is truncate.
>  If a process writes 1 MB to a file and then deletes the file,
>  it will in fact perform no writeout.
>  But it will have been accounted as having caused 1 MB of write.
> -In other words: this field represents the number of bytes which this process
> +In other words:
> +this field represents the number of bytes
> +which this process and its waited-for children
>  caused to not happen, by truncating pagecache.
>  A task can cause "negative" I/O too.
>  If this task truncates some dirty pagecache,
> -- 
> 2.39.2
> 



-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-03-17 11:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 14:26 [PATCH 1/6] proc_pid_io.5: stats include children наб
2024-03-13 14:26 ` [PATCH 2/6] proc_pid_io.5: dewafflify наб
2024-03-14 16:21   ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 3/6] proc_pid_io.5: wfix наб
2024-03-14 16:22   ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 4/6] proc_pid_io.5: mention atomicity in atomicity note наб
2024-03-14 16:28   ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 5/6] getrusage.2: proc(5) /proc/pid/stat -> proc_pid_stat(5) наб
2024-03-14 16:31   ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 6/6] getrusage.2, proc_pid_io.5: crosslink наб
2024-03-14 16:33   ` Alejandro Colomar
2024-03-14 16:19 ` [PATCH 1/6] proc_pid_io.5: stats include children Alejandro Colomar
2024-03-17 11:01 ` [PATCH v2 2/2] proc_pid_io.5: dewafflify наб
2024-03-17 12:15   ` Alejandro Colomar
2024-03-17 13:31     ` [PATCH v3] " наб
2024-03-17 14:12       ` Alejandro Colomar
2024-03-17 15:37         ` [PATCH v4] " наб
2024-03-17 16:08           ` Alejandro Colomar
2024-03-17 11:01 ` [PATCH v2 1/2] proc_pid_io.5: stats include children наб
2024-03-17 11:39   ` Alejandro Colomar [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=ZfbWaLu0o6towx2W@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.