linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: ykzhao <yakui.zhao@intel.com>,
	chen gong <gong.chen@linux.intel.com>,
	Matthew Garrett <mjg@redhat.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [RFC PATCH]: ACPI: Automatically online hot-added memory
Date: Fri, 19 Mar 2010 13:23:33 -0400	[thread overview]
Message-ID: <4BA3B315.6080905@redhat.com> (raw)
In-Reply-To: <201003191755.35421.trenn@suse.de>


>
> Blocking does not work.
> But I have an idea, whatabout:
>   - CPU add rule which only adds a CPU if the corresponding Numa node already
>     has onlined memory
>   - Memory add rule which adds the memory and also onlines CPUs if the Numa
>     node still has offlined CPUs
>
> This has the side effect that you online a CPU which may have been offlined on
> purpose if you hotadd memory on the same node..., a rather uncommon case.
>
>   
That actually might be more of a problem than you think.  It's not 
atypical that in the evening a system's components are offlined in order 
to save power.  Maintenance also is scheduled for downtime so when 
memory is added to the system we may bring cpus into service 
erroneously.  I think the "end-user" may not be too happy with this result.

[OTOH, a little documentation could fix that issue]

> A quick try showed that it would be convenient to add the Numa node to the 
> uevent which is a bit tricky...
> Ok, I got this working, but messed up the cpu hotplugging with my patches:
> ...
> Unable to map lapic 32 to logical cpu number
> ...
> This already worked...
>
> I wanted to post something today, but I couldn't made it.
> Still I more or less could prove that above works and I hopefully can show
> some results on Monday.
>
>   

If it works then I'm all for it :)

> Comments?
>
>    Thomas
>
> BTW: I was wrong with slub. It also has bad side effects. What is strange is 
>   

FWIW, I'm testing with slab.

P.


  reply	other threads:[~2010-03-19 17:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 14:12 [RFC PATCH]: ACPI: Automatically online hot-added memory Prarit Bhargava
2010-03-09 15:42 ` Matthew Garrett
2010-03-09 18:27   ` Prarit Bhargava
2010-03-10  1:57     ` ykzhao
2010-03-10 13:28       ` Prarit Bhargava
2010-03-11  0:55         ` ykzhao
2010-03-11  2:18           ` Prarit Bhargava
2010-03-11  8:07             ` ykzhao
2010-03-11  8:32               ` chen gong
2010-03-11 11:25                 ` Prarit Bhargava
2010-03-12 13:18                 ` Thomas Renninger
2010-03-17 18:47                   ` Prarit Bhargava
2010-03-19 16:55                     ` Thomas Renninger
2010-03-19 17:23                       ` Prarit Bhargava [this message]
2010-03-20 20:51                         ` Thomas Renninger
2010-03-24 14:40                     ` Thomas Renninger
2010-03-24 15:16                       ` Prarit Bhargava
2010-03-11 11:18               ` Prarit Bhargava
2010-03-12  1:31                 ` ykzhao
2010-03-12 13:01           ` Thomas Renninger
2010-03-17 15:24             ` Prarit Bhargava
2010-03-09 19:10 ` Alex Chiang
2010-03-09 19:15   ` Prarit Bhargava

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=4BA3B315.6080905@redhat.com \
    --to=prarit@redhat.com \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).