public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kingsley Cheung <kingsley@aurema.com>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] For preventing kstat overflow
Date: Wed, 10 Mar 2004 10:13:47 +1100	[thread overview]
Message-ID: <20040310101347.B30341@aurema.com> (raw)
In-Reply-To: <20040309165704.L29788@aurema.com>; from kingsley@aurema.com on Tue, Mar 09, 2004 at 04:57:04PM +1100

On Tue, Mar 09, 2004 at 04:57:04PM +1100, Kingsley Cheung wrote:
> On Mon, Mar 08, 2004 at 06:53:54PM -0800, Andrew Morton wrote:
> > Kingsley Cheung <kingsley@aurema.com> wrote:
> > >
> > > Hi All,
> > > 
> > > What do people think of a patch to change the fields in cpu_usage_stat
> > > from unsigned ints to unsigned long longs?  And the same change for
> > > nr_switches in the runqueue structure too?
> > 
> > Sounds unavoidable.
> > 
> > > Its actually worse for context
> > > switches on a busy system, for we've been seeing an average of ten
> > > switches a tick for some of the statistics we have.
> > 
> > Sounds broken.  What CPU scheduler are you using?
> 
> Um, what do you mean by broken?
> 
> Well, as for the scheduler, its the Entitlement Based Scheduler, but
> it doesn't look like its got anything to do with the scheduler.  Some
> work loads we have been testing just have processes that come and go
> so frequently that the context switch rate is high.  Even when Ingo
> posted his original O(1) patch (see
> http://marc.theaimsgroup.com/?l=linux-kernel&m=101010394225604&w=2) he
> claimed high context switch rates.

Oh, just in case there's some confusion... even though we've been
seeing it for EBS, the patch is for 2.6.3.

-- 
		Kingsley

      reply	other threads:[~2004-03-09 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09  2:23 [PATCH] For preventing kstat overflow Kingsley Cheung
2004-03-09  2:53 ` Andrew Morton
2004-03-09  5:57   ` Kingsley Cheung
2004-03-09 23:13     ` Kingsley Cheung [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=20040310101347.B30341@aurema.com \
    --to=kingsley@aurema.com \
    --cc=akpm@osdl.org \
    --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