From: William Lee Irwin III <wli@holomorphy.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>,
Keith Owens <kaos@ocs.com.au>, Linus Torvalds <torvalds@osdl.org>,
Pavel Machek <pavel@ucw.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH][2.6] Completely out of line spinlocks / i386
Date: Thu, 12 Aug 2004 00:25:31 -0700 [thread overview]
Message-ID: <20040812072531.GJ11200@holomorphy.com> (raw)
In-Reply-To: <20040812072338.GI11200@holomorphy.com>
On Thu, Aug 12, 2004 at 12:20:58AM -0700, William Lee Irwin III wrote:
>> Okay, the results on 2.6.8-rc4 (COOL had a bit of porting, basically
>> dropping the hunks associated with spin_lock_flags_string or whatever
>> it is). Chose the .config largely to be vaguely deterministic, but had
>> to nuke the "System is too big" check in arch/x86_64/boot/tools/build.c.
>> text data bss dec hex filename
>> mainline: 20708323 6603052 1878448 29189823 1bd66bf vmlinux
>> cool: 20619594 6588166 1878448 29086208 1bbd200 vmlinux
>> C-func: 19969264 6583128 1878384 28430776 1b1d1b8 vmlinux
>> x86-64, -O2, allyesconfig minus the following:
> [...]
On Thu, Aug 12, 2004 at 12:23:38AM -0700, William Lee Irwin III wrote:
> The precise COOL patch used:
For completeness, the "System is too big" avoidance patch, too.
Please don't merge this. It's just "full disclosure" for how I ran this
particular compiletest.
Index: spinlock-2.6.8-rc4/arch/x86_64/boot/tools/build.c
===================================================================
--- spinlock-2.6.8-rc4.orig/arch/x86_64/boot/tools/build.c 2004-06-15 22:20:27.000000000 -0700
+++ spinlock-2.6.8-rc4/arch/x86_64/boot/tools/build.c 2004-08-11 23:22:43.242607520 -0700
@@ -151,9 +151,6 @@
fprintf (stderr, "System is %d kB\n", sz/1024);
sys_size = (sz + 15) / 16;
/* 0x40000*16 = 4.0 MB, reasonable estimate for the current maximum */
- if (sys_size > (is_big_kernel ? 0x40000 : DEF_SYSSIZE))
- die("System is too big. Try using %smodules.",
- is_big_kernel ? "" : "bzImage or ");
while (sz > 0) {
int l, n;
next prev parent reply other threads:[~2004-08-12 7:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 4:49 [PATCH][2.6] Completely out of line spinlocks / i386 Zwane Mwaikambo
2004-08-08 5:01 ` Linus Torvalds
2004-08-08 5:17 ` Zwane Mwaikambo
2004-08-08 5:21 ` Linus Torvalds
2004-08-08 6:00 ` Zwane Mwaikambo
2004-08-08 12:33 ` Andreas Schwab
2004-08-08 18:26 ` Zwane Mwaikambo
2004-08-11 21:59 ` Pavel Machek
2004-08-11 22:13 ` Linus Torvalds
2004-08-11 22:23 ` William Lee Irwin III
2004-08-12 0:01 ` Keith Owens
2004-08-12 0:39 ` David S. Miller
2004-08-12 0:54 ` Zwane Mwaikambo
2004-08-12 1:01 ` William Lee Irwin III
2004-08-12 1:37 ` Zwane Mwaikambo
2004-08-12 2:04 ` William Lee Irwin III
2004-08-12 7:20 ` William Lee Irwin III
2004-08-12 7:23 ` William Lee Irwin III
2004-08-12 7:25 ` William Lee Irwin III [this message]
2004-08-12 8:12 ` Zwane Mwaikambo
2004-08-12 8:11 ` William Lee Irwin III
2004-08-12 8:54 ` William Lee Irwin III
2004-08-13 8:01 ` William Lee Irwin III
2004-08-13 9:16 ` William Lee Irwin III
2004-08-13 9:30 ` William Lee Irwin III
2004-08-13 9:46 ` William Lee Irwin III
2004-08-13 10:05 ` William Lee Irwin III
2004-08-13 10:23 ` William Lee Irwin III
2004-08-13 10:39 ` William Lee Irwin III
2004-08-13 14:15 ` Zwane Mwaikambo
2004-08-13 14:29 ` 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=20040812072531.GJ11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pavel@ucw.cz \
--cc=torvalds@osdl.org \
--cc=zwane@linuxpower.ca \
/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