public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Gerlof Langeveld <gerlof@ATComputing.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] accounting: task counters for disk/network
Date: Thu, 3 Apr 2008 12:54:16 -0700	[thread overview]
Message-ID: <20080403125416.ead5cd38.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080402073037.GA8419@atcmpg.ATComputing.nl>

On Wed, 2 Apr 2008 09:30:37 +0200
Gerlof Langeveld <gerlof@ATComputing.nl> wrote:

> 
> From: Gerlof Langeveld <gerlof@atcomputing.nl>

You sent three different patches, all with the same title.  Please don't do
that - choose unique, suitable and meaningful titles for each patch.

> Proper performance analysis requires the availability of system level
> and process level counters for CPU, memory, disk and network utilization.
> The current kernel offers the system level counters, however process level
> counters are only (sufficiently) available for CPU and memory utilization.
> 
> The kernel feature "task I/O accounting" currently maintains
> per process counters for the number of bytes transferred to/from disk.
> These counters are available via /proc/pid/io. It is still not possible
> to find out which process issues the physical disk transfer. Besides,
> not *all* disk transfers are accounted to processes (e.g. swap-transfers
> by kswapd, journaling transfers).
> 
> This patch extends "task I/O accounting" by counting real *physical*
> disk transfers per process and by counting IPv4/IPv6 socket transfers
> per process.
> The modified output generated for /proc/pid/io will be as follows:
> 
>   $ cat /proc/3179/io

/proc/pid/io is not the primary interface for this sort of accounting - it
was just tossed in there as an afterthought because it wasy easy.

This sort of accounting should be delivered across taskstats and
Documentation/accounting/getdelays.c should be suitably updated.

> --- linux-2.6.24.4-vanilla/block/ll_rw_blk.c	2008-03-24 19:49:18.000000000 +0100
> +++ linux-2.6.24.4-modified/block/ll_rw_blk.c	2008-03-25 13:52:14.000000000 +0100
> @@ -2739,6 +2739,19 @@ static void drive_stat_acct(struct reque
>  		disk_round_stats(rq->rq_disk);
>  		rq->rq_disk->in_flight++;
>  	}
> +
> +#ifdef CONFIG_TASK_IO_ACCOUNTING
> +	switch (rw) {
> +	case READ:
> +		current->group_leader->ioac.dsk_rio += new_io;
> +		current->group_leader->ioac.dsk_rsz += rq->nr_sectors;
> +		break;
> +	case WRITE:
> +		current->group_leader->ioac.dsk_wio += new_io;
> +		current->group_leader->ioac.dsk_wsz += rq->nr_sectors;
> +		break;
> +	}
> +#endif

For many workloads, this will cause almost all writeout to be accounted to
pdflush and perhaps kswapd.  This makes the per-task write accounting
largely unuseful.


  reply	other threads:[~2008-04-03 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02  7:30 [PATCH 1/3] accounting: task counters for disk/network Gerlof Langeveld
2008-04-03 19:54 ` Andrew Morton [this message]
2008-04-08  5:48   ` Gerlof Langeveld
2008-04-08  6:10     ` Andrew Morton
2008-04-08  6:16       ` Paul Menage
2008-04-10  3:41         ` Hirokazu Takahashi

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=20080403125416.ead5cd38.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gerlof@ATComputing.nl \
    --cc=linux-kernel@vger.kernel.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