public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Lahti Oy <rlahti@netikka.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched.c
Date: Tue, 27 Aug 2002 11:35:49 -0700	[thread overview]
Message-ID: <3D6BC685.216B5B67@zip.com.au> (raw)
In-Reply-To: 000b01c24df5$aacc7ed0$d20a5f0a@deldaran

Lahti Oy wrote:
> 
> Small patch that makes NR_CPUS loops decrement from 31 to 0 in sched.c to
> squeeze out some cycles (of course only on SMP machines). Also deprecated a
> macro that was only used once in the code and changed one if-conditional to
> else if.
> 
> ...
> 
> - for (i = 0; i < NR_CPUS; i++)
> + for (i = NR_CPUS; i; i--)
>    sum += cpu_rq(i)->nr_running;

Off-by-one there.  You'd want

	for (i = NR_CPUS; --i >= 0; )

or something similarly foul ;)

But these are not performance-critical functions.  And by far the
most inefficient part of them is that they're reading data for
CPUs which cannot exist.   That can be fixed with a `cpu_possible(i)'
test in there, but Rusty was going to give us a `for_each_cpu' macro.
We haven't seen that yet.

  parent reply	other threads:[~2002-08-27 18:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 18:15 [PATCH] sched.c Lahti Oy
2002-08-27 18:33 ` Willy Tarreau
2002-08-27 18:35 ` Andrew Morton [this message]
2002-08-28  0:13   ` Daniel Phillips
2002-08-28  0:41     ` Andreas Dilger
2002-08-28  0:51       ` Daniel Phillips
2002-08-28  0:44     ` Stephen C. Biggs
2002-08-28  0:47     ` Daniel Phillips
2002-08-28  0:59       ` Stephen C. Biggs
2002-08-28 13:45         ` Thunder from the hill
2002-08-28  6:47   ` Rusty Russell

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=3D6BC685.216B5B67@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlahti@netikka.fi \
    /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