From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mike Travis <travis@sgi.com>
Subject: Re: [git pull] cpus4096 fixes
Date: Mon, 28 Jul 2008 10:53:57 +1000 [thread overview]
Message-ID: <200807281053.58267.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080727190601.GA764@elte.hu>
On Monday 28 July 2008 05:06:01 Ingo Molnar wrote:
> Linus,
>
> Please pull the latest cpus4096-fixes git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
> cpus4096
>
> this fixes the cpumask_of_cpu API fallout described here:
>
> http://lkml.org/lkml/2008/7/23/76
>
> ... and the fix is wider than i'd like it to be, so close to -rc1
Sorry, it's wider because you pushed the last stupid Mike patch. Over my
(obviously too-polite) objections. Most of this is reverting that, just
without actually admitting it.
> - but
> it's the cleanest one and it has Rusty's ack as well.
Not really. As authored, I intended it as a bandaid for systems with small
CPU numbers. Mike made it always on (tho __initdata on large x86 systems),
which IMHO is insane (2MB of initdata?).
Mike: I now think the right long-term answer is Linus' dense cpumap idea + a
convenience allocator for cpumasks. We sweep the kernel for all on-stack
vars and replace them with one or the other. Thoughts?
Rusty.
next prev parent reply other threads:[~2008-07-28 0:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 19:06 [git pull] cpus4096 fixes Ingo Molnar
2008-07-27 20:15 ` Linus Torvalds
2008-07-27 21:03 ` Ingo Molnar
2008-07-28 18:42 ` Mike Travis
2008-07-27 21:05 ` Al Viro
2008-07-27 22:17 ` Linus Torvalds
2008-07-28 0:42 ` Rusty Russell
2008-07-28 3:06 ` Andrew Morton
2008-07-28 6:34 ` Rusty Russell
2008-07-28 6:58 ` Nick Piggin
2008-07-28 7:56 ` Ingo Molnar
2008-07-28 18:12 ` Mike Travis
2008-07-28 8:33 ` Ingo Molnar
2008-07-28 18:07 ` Mike Travis
2008-07-28 17:50 ` Mike Travis
2008-07-28 18:32 ` Linus Torvalds
2008-07-28 18:37 ` Linus Torvalds
2008-07-28 18:51 ` Ingo Molnar
2008-07-28 19:22 ` Mike Travis
2008-07-28 19:31 ` Mike Travis
2008-07-28 19:04 ` Mike Travis
2008-07-28 20:57 ` [rfc git pull] cpus4096 fixes, take 2 Ingo Molnar
2008-07-28 21:35 ` Ingo Molnar
2008-07-28 21:41 ` [build error] drivers/char/pcmcia/ipwireless/hardware.c:571: error: invalid use of undefined type 'struct ipw_network' Ingo Molnar
2008-07-28 22:06 ` Ingo Molnar
2008-07-28 22:20 ` Andrew Morton
2008-07-28 22:29 ` Ingo Molnar
2008-07-30 14:59 ` David Sterba
2008-07-30 15:11 ` James Bottomley
2008-07-30 15:14 ` Jiri Kosina
2008-07-28 21:36 ` [rfc git pull] cpus4096 fixes, take 2 Mike Travis
2008-07-29 1:45 ` Rusty Russell
2008-07-29 12:11 ` Ingo Molnar
2008-07-30 0:15 ` Rusty Russell
2008-07-28 18:46 ` [git pull] cpus4096 fixes Mike Travis
2008-07-28 19:13 ` Ingo Molnar
2008-07-29 1:33 ` Rusty Russell
2008-07-28 0:53 ` Rusty Russell [this message]
2008-07-28 8:16 ` Ingo Molnar
2008-07-28 13:21 ` Rusty Russell
2008-07-28 18:23 ` Mike Travis
2008-07-31 10:30 ` Ingo Molnar
2008-07-28 8:43 ` Ingo Molnar
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=200807281053.58267.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.