public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, torvalds@transmeta.com
Subject: Re: O(1) count_active_tasks()
Date: Tue, 28 May 2002 11:56:20 -0700	[thread overview]
Message-ID: <20020528185620.GS14918@holomorphy.com> (raw)
In-Reply-To: <20020526035115.GM14918@holomorphy.com> <1022451477.20316.24.camel@sinai> <20020526230319.GN14918@holomorphy.com> <1022599985.20316.32.camel@sinai> <1022609318.20317.65.camel@sinai>

On Tue, May 28, 2002 at 11:08:35AM -0700, Robert Love wrote:
> Well, I did some tests.  I changed count_active_tasks to calculate using
> both methods and whine if they did not match.  I then put the machine
> under extreme load with a lot of I/O.  Finally, I ran `uptime(1)' in a
> tight loop and watched the console.
> Over a long period of constant count_active_tasks calls via `uptime(1)',
> I had only a couple messages.  This is most likely <=1% of the calls and
> in each case we were one to high with the new method (140 vs 141, for
> example).
> Not sure why, or if it is even us or nr_running() or even the old method
> that is off ... but who cares.  It is a statistic.


Thanks a million for doing some independent testing! I should have
been more clear about the fact that it was an approximate method, and
that it varies from mainline occasionally and slightly. But this is the
nature of the patch I proposed.


Thanks,
Bill

      reply	other threads:[~2002-05-28 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-26  3:51 O(1) count_active_tasks() William Lee Irwin III
2002-05-26 22:17 ` Robert Love
2002-05-26 23:03   ` William Lee Irwin III
2002-05-28 15:33     ` Robert Love
2002-05-28 18:08       ` Robert Love
2002-05-28 18:56         ` William Lee Irwin III [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=20020528185620.GS14918@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@tech9.net \
    --cc=torvalds@transmeta.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