mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jay Lan <jlan@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, nagar@watson.ibm.com,
	balbir@in.ibm.com, jes@sgi.com, csturtiv@sgi.com, tee@sgi.com,
	guillaume.thouvenin@bull.net
Subject: Re: [patch 1/3] basic accounting over taskstats
Date: Wed, 2 Aug 2006 23:52:19 -0700	[thread overview]
Message-ID: <20060802235219.25a072e7.akpm@osdl.org> (raw)
In-Reply-To: <44D179A5.4000606@engr.sgi.com>

On Wed, 02 Aug 2006 21:20:53 -0700
Jay Lan <jlan@engr.sgi.com> wrote:

> This patch is to replace the "[patch 1/3] add basic accounting
> fields to taskstats" posted on 7/31.
> 
> This patch adds some basic accounting fields to the taskstats
> struct, add a new kernel/tsacct.c to handle basic accounting
> data handling upon exit. A handle is added to taskstats.c
> to invoke the basic accounting data handling.
> 

> +#define TS_COMM_LEN		16	/* should sync up with TASK_COMM_LEN
> +					 * in linux/sched.h */

There was a proposal recently to increase TASK_COMM_LENGTH from 16 to 20 so
that it was long enough to hold an entire IEEE(?) UUID so that the
operator can easily match up a kernel thread with the storage device which
it manages.

I don't know if/when that change will happen, but the message is that
TASK_COMM_LENGTH may increase.

> +	BUILD_BUG_ON(TS_COMM_LEN < TASK_COMM_LEN);

And if it does, we'll need to increase TS_COMM_LEN as well.  That will
amount to an non-compatible change to the interface which you are
proposing.   We want to avoid that.

Hence I'd propose that you increase TS_COMM_LEN to 32 or something and if
TASK_COMM_LEN later becomes really big, we might just choose to truncate
it.

Or we remove this field altogether, perhaps.  The same info is available
from /proc/pid/stat anyway.  Is it really needed?


  reply	other threads:[~2006-08-03  6:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  4:20 Jay Lan
2006-08-03  6:52 ` Andrew Morton [this message]
2006-08-03 13:56   ` Shailabh Nagar
2006-08-03 18:48     ` Jay Lan
2006-08-03 19:29       ` Shailabh Nagar

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=20060802235219.25a072e7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=balbir@in.ibm.com \
    --cc=csturtiv@sgi.com \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jes@sgi.com \
    --cc=jlan@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nagar@watson.ibm.com \
    --cc=tee@sgi.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

Powered by JetHome