public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Chapman <doug.chapman@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [REGRESSION] Minimize per_cpu reservations patch causes NULL
Date: Tue, 04 Nov 2008 21:21:49 +0000	[thread overview]
Message-ID: <1225833709.13942.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1225830514.13942.8.camel@localhost.localdomain>

On Tue, 2008-11-04 at 13:12 -0800, Luck, Tony wrote:
> > 1) try to get the info regarding offline CPUs earlier either by calling
> > acpi_boot_init() earlier (probably not possible prior to calling find_memory())
> > or walk a subset of the ACPI tables to get the number of offline CPUs sooner
> > (which sounds ugly).
> >
> >
> > 2) after we call acpi_boot_init() go back and setup the per-cpu datastructures
> > for the offline CPUs then.  Seems like this might be cleaner but I have not
> > investigated the specifics.
> 
> What about:
> 
> 3) Perform the needed allocations when we try to bring the new cpu online?

Seems logical, we would need to fix the code that is trying to use the
datastructures for offline CPUs however.  The panic we current hit is in
migration_thread and that might be the only case.

> 
> It is possible that this will fail ... but if you are so low on memory
> that you can't allocate a couple of pages for the new cpu, you are in
> a world of hurt already and adding a new cpu is liklely to make things
> worse.

The patch that caused this doesn't just prevent allocating structures
for the offline CPUs but prevents allocating NR_CPUS (4096 in the case
of SLES11) per-cpu structures on a small system that has perhaps only 4
CPUs.

- Doug



  parent reply	other threads:[~2008-11-04 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 20:28 [REGRESSION] Minimize per_cpu reservations patch causes NULL ptr Doug Chapman
2008-11-04 20:35 ` [REGRESSION] Minimize per_cpu reservations patch causes NULL Doug Chapman
2008-11-04 21:12 ` Luck, Tony
2008-11-04 21:21 ` Doug Chapman [this message]
2008-11-05 23:07 ` Doug Chapman

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=1225833709.13942.17.camel@localhost.localdomain \
    --to=doug.chapman@hp.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