All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] Fix large MCA bootmem allocation
Date: Wed, 06 Feb 2008 10:44:39 +0000	[thread overview]
Message-ID: <20080206104438.GE3875@sgi.com> (raw)
In-Reply-To: <20080205193232.GA8834@sgi.com>

On Wed, Feb 06, 2008 at 12:50:11PM +0900, Hidetoshi Seto wrote:
> Hidetoshi Seto wrote:
>> Then, I suppose we need a CPU_UP_PREPARE callback to allocate memory
>> before hot-added CPU enters cpu_init().
>
> Ah, we cannot allocate bootmem later, so it would be better to make
> the callback to return NOTIFY_BAD if (!__per_cpu_mca[hcpu]).
>

bootmem is only used for the first cpu.  The other cpus use regular
allocations.  So we should be able to do a CPU_UP_PREPARE.

Comparing the severity of allocating a ton of extra memory with the
chance that we fail on an allocation and given that there are likely
other things in the cpu_init path which are not checked, do you see the
lack of check as a show-stopper for this patch or would you accept this
patch with the plan being fixup the cpu_init path later?

Thanks,
Robin

  parent reply	other threads:[~2008-02-06 10:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 19:32 [patch] Fix large MCA bootmem allocation Russ Anderson
2008-02-05 20:21 ` Bjorn Helgaas
2008-02-05 23:12 ` Russ Anderson
2008-02-05 23:24 ` Bjorn Helgaas
2008-02-05 23:54 ` Luck, Tony
2008-02-05 23:54 ` Russ Anderson
2008-02-06  0:00 ` Luck, Tony
2008-02-06  0:30 ` Hidetoshi Seto
2008-02-06  1:34 ` Robin Holt
2008-02-06  2:23 ` Hidetoshi Seto
2008-02-06  3:50 ` Hidetoshi Seto
2008-02-06 10:44 ` Robin Holt [this message]
2008-02-06 12:39 ` Hidetoshi Seto
2008-02-06 13:22 ` Robin Holt
2008-02-06 15:13 ` Russ Anderson
2008-02-06 23:32 ` Russ Anderson

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=20080206104438.GE3875@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 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.