From: hawkes@sgi.com
To: linux-kernel@vger.kernel.org
Cc: hawkes@sgi.com
Subject: [PATCH] 2.6.14-rc4: wider use of for_each_*cpu() in mm
Date: Thu, 13 Oct 2005 12:01:50 -0700 (PDT) [thread overview]
Message-ID: <20051013190150.13195.77414.sendpatchset@tomahawk.engr.sgi.com> (raw)
In 'mm' change the explicit use of a for-loop using NR_CPUS into the
general for_each_cpu() constructs. This widens the scope of potential
future optimizations of the general constructs, as well as takes
advantage of the existing optimizations of first_cpu() and next_cpu(),
which is advantageous when the true CPU count is much smaller than NR_CPUS.
Signed-off-by: John Hawkes <hawkes@sgi.com>
Index: linux/mm/page_alloc.c
===================================================================
--- linux.orig/mm/page_alloc.c 2005-10-13 09:29:53.000000000 -0700
+++ linux/mm/page_alloc.c 2005-10-13 09:30:36.000000000 -0700
@@ -1305,12 +1305,9 @@
} else
printk("\n");
- for (cpu = 0; cpu < NR_CPUS; ++cpu) {
+ for_each_cpu(cpu) {
struct per_cpu_pageset *pageset;
- if (!cpu_possible(cpu))
- continue;
-
pageset = zone_pcp(zone, cpu);
for (temperature = 0; temperature < 2; temperature++)
reply other threads:[~2005-10-13 19:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051013190150.13195.77414.sendpatchset@tomahawk.engr.sgi.com \
--to=hawkes@sgi.com \
--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
Powered by JetHome