mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tom Burns" <tom.i.burns@gmail.com>
To: "Tim Schmielau" <tim@physik3.uni-rostock.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug: 2.6.15 Process accounting fails to account for small time slice loads (still)
Date: Tue, 30 Jan 2007 13:56:48 -0500	[thread overview]
Message-ID: <671c20540701301056l6ff1d876xb8df0d9d83ea2c8a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701301840470.14441@gockel.physik3.uni-rostock.de>

Hi Tim.

That would be great if you could find that patch - I can worry about
porting it to the current kernel.  We're having an issue where our
device, while routing large amounts of network traffic, reports 0% CPU
utilisation when it cannot be the case, and I think this is the cause.

Cheers,
Tom Burns

On 1/30/07, Tim Schmielau <tim@physik3.uni-rostock.de> wrote:
> On Tue, 30 Jan 2007, Tom Burns wrote:
>
> > The bug described back in 2004 in the following message still seems to exist:
> >
> > http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-05/4313.html
> >
> > Essentially, it appears that if a process sleeps before it uses up a
> > complete jiffy then no charge is made to its process accounting table.
>
> That's not a bug, it's a feature. ;-)
>
> More seriously, it's a design decision. The benefit of exactly correct
> micro bookkeeping does not seem to warrant the extra cost in terms of cpu
> cycles spent in the accounting code.
>
> IIRC there was a patch for that some years ago, if you are interested I
> will try to find it. No idea how much work it would be to port it to
> current kernels, though.
>
> Tim
>

  reply	other threads:[~2007-01-30 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 16:24 Tom Burns
2007-01-30 16:54 ` Tom Burns
2007-01-30 17:48 ` Tim Schmielau
2007-01-30 18:56   ` Tom Burns [this message]
2007-01-30 21:13     ` Tim Schmielau
2007-01-30 19:25 ` Christian Borntraeger

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=671c20540701301056l6ff1d876xb8df0d9d83ea2c8a@mail.gmail.com \
    --to=tom.i.burns@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.de \
    /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

all inboxes | Powered by JetHome®