linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Schmielau <tim@physik3.uni-rostock.de>
To: Rolf Fokkens <fokkensr@fokkensr.vertis.nl>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 32bit wraps and USER_HZ [64 bit counters], kernel 2.5.37
Date: Tue, 24 Sep 2002 13:47:38 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0209241342470.4261-100000@gans.physik3.uni-rostock.de> (raw)
In-Reply-To: <200209232208.g8NM8bN05831@fokkensr.vertis.nl>

On Tue, 24 Sep 2002, Rolf Fokkens wrote:
> On Monday 23 September 2002 04:36, William Lee Irwin III wrote:
> > -	unsigned long utime, stime, cutime, cstime;
> > -	unsigned long start_time;
> > -	long per_cpu_utime[NR_CPUS], per_cpu_stime[NR_CPUS];
> >
> > Hmm. Isn't task_t bloated enough already? I'd rather remove them than
> > make them 64-bit.
> 
> Since nobody else asks this question:
> 
> Do you mean to leave out process statistics?

We don't need to leave out process statistics completely, but per-CPU 
per-process statistics indeed looks like overkill.

Tim

P.S.: Some work with respect to cleaning up interfaces of 32 bit jiffies 
has gone into -dj already, but I'm still waiting for the next -dj release 
to sync up.


  parent reply	other threads:[~2002-09-24 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-22 22:07 [PATCH] 32bit wraps and USER_HZ [64 bit counters], kernel 2.5.37 Rolf Fokkens
2002-09-23  2:36 ` William Lee Irwin III
2002-09-23 22:08   ` Rolf Fokkens
2002-09-23 22:13     ` Robert Love
2002-09-24  7:04       ` Rolf Fokkens
2002-09-24  7:11         ` William Lee Irwin III
2002-09-24 11:47     ` Tim Schmielau [this message]
2002-09-24 11:50       ` William Lee Irwin III

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=Pine.LNX.4.33.0209241342470.4261-100000@gans.physik3.uni-rostock.de \
    --to=tim@physik3.uni-rostock.de \
    --cc=fokkensr@fokkensr.vertis.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).