public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: Re: percpu-2.5.63-bkcurr
Date: Fri, 28 Feb 2003 23:46:16 -0800	[thread overview]
Message-ID: <20030301074616.GC1195@holomorphy.com> (raw)
In-Reply-To: <20030301074035.GB1195@holomorphy.com>

On Fri, Feb 28, 2003 at 11:36:55PM -0800, William Lee Irwin III wrote:
> Tentative followup #1 (thanks Zwane!)
>> Use per-cpu rq's in the sched.c to avoid remote cache misses there.
>> It actually means something now.

On Fri, Feb 28, 2003 at 11:40:35PM -0800, William Lee Irwin III wrote:
> Tentative followup #2 -- totally untested, at some point I have to
> figure out how to avoid breaking the compile for non-NUMA-Q with this.

woops


diff -u sched-2.5/arch/i386/mm/discontig.c sched-2.5/arch/i386/mm/discontig.c
--- sched-2.5/arch/i386/mm/discontig.c	Fri Feb 28 23:12:45 2003
+++ sched-2.5/arch/i386/mm/discontig.c	Fri Feb 28 23:42:15 2003
@@ -230,6 +230,7 @@
 	for (nid = 1; nid < numnodes; nid++) {
 		/* calculate the size of the mem_map needed in pages */
 		size = MEM_MAP_SIZE(nid) + PFN_UP(sizeof(pg_data_t))
+			+ PER_NODE_PAGES
 			+ PER_CPU_PAGES*hweight32(early_node_to_cpumask(nid));
 		/* round up to nearest pmd boundary */
 		size = (size + PTRS_PER_PTE - 1) & ~(PTRS_PER_PTE - 1);

  reply	other threads:[~2003-03-01  7:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01  5:59 percpu-2.5.63-bkcurr William Lee Irwin III
2003-03-01  7:36 ` percpu-2.5.63-bkcurr William Lee Irwin III
2003-03-01  7:40   ` percpu-2.5.63-bkcurr William Lee Irwin III
2003-03-01  7:46     ` William Lee Irwin III [this message]
2003-03-01  8:27       ` percpu-2.5.63-bkcurr William Lee Irwin III

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=20030301074616.GC1195@holomorphy.com \
    --to=wli@holomorphy.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