From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Reduce per_cpu allocations to the minimum needed for
Date: Wed, 13 Feb 2008 16:38:59 +0000 [thread overview]
Message-ID: <20080213163859.GA23324@sgi.com> (raw)
In-Reply-To: <20080211175918.GO3875@sgi.com>
Christoph,
If you point me at that patch, I would happily resurrect it and see if
I can get it worked in. I will be working on that in the evenings so
my progress will be slow.
Thanks,
Robin
On Tue, Feb 12, 2008 at 10:53:41AM -0800, Christoph Lameter wrote:
> On Tue, 12 Feb 2008, Robin Holt wrote:
>
> > Please don't apply this yet. I just noticed the CONFIG_FLATMEM configs
> > did not work. I will look at this more this evening.
>
> That reminds me: I have a patch to remove all other memory models except
> for SPARSE_VMEMMAP for ia64 somewhere.... If we would merge that then
> maintaining ia64 may become simpler.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-02-13 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 17:59 [PATCH] Reduce per_cpu allocations to the minimum needed for boot Robin Holt
2008-02-11 18:09 ` Robin Holt
2008-02-12 18:49 ` [PATCH] Reduce per_cpu allocations to the minimum needed for Robin Holt
2008-02-12 18:53 ` Christoph Lameter
2008-02-13 0:34 ` [PATCH] Reduce per_cpu allocations to the minimum needed for boot -V5 Luck, Tony
2008-02-13 3:20 ` [PATCH] Reduce per_cpu allocations to the minimum needed for boot Robin Holt
2008-02-13 3:23 ` [PATCH] Reduce per_cpu allocations to the minimum needed for Robin Holt
2008-02-13 13:19 ` Robin Holt
2008-02-13 15:03 ` Robin Holt
2008-02-13 16:38 ` Robin Holt [this message]
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=20080213163859.GA23324@sgi.com \
--to=holt@sgi.com \
--cc=linux-ia64@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