mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, Tejun Heo <tj@kernel.org>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Correct nr_processes() when CPUs have been unplugged
Date: Wed, 4 Nov 2009 11:42:04 +0100	[thread overview]
Message-ID: <20091104104204.GA13194@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0911031324380.32136@V090114053VZO-1>


* Christoph Lameter <cl@linux-foundation.org> wrote:

> On Tue, 3 Nov 2009, Ingo Molnar wrote:
> 
> > Sidenote: percpu areas currently are kept allocated on x86.
> 
> They must be kept allocated for all possible cpus. Arch code cannot 
> decide to not allocate per cpu areas.
> 
> Search for "for_each_possible_cpu" in the source tree if you want more 
> detail.

This has come up in the past. On-demand deallocation of percpu areas is 
a future possibility that might be useful - see previous percpu 
discussions on lkml for details.

All in one, the conclusion is that we dont want it yet (on-demand 
allocation of them is perfectly fine for now) - i just wanted to mention 
that this is a _current_ situation and an implementational choice, which 
judgement could change in the future.

The more 'virtual' our abstraction of CPUs becomes, the less the notion 
of permanent allocation will be acceptable as time goes on.

Dynamic allocation concepts are natural and the new, generic percpu 
allocator makes it more feasible to eventually deallocate percpu areas. 
(Of course various for_each_possible_cpu() assumptions will have to be 
fixed in that case.)

	Ingo

  parent reply	other threads:[~2009-11-04 10:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 10:11 Ian Campbell
2009-11-03 15:51 ` Linus Torvalds
2009-11-03 16:07 ` Ingo Molnar
2009-11-03 18:34   ` Christoph Lameter
2009-11-04  6:09     ` Paul E. McKenney
2009-11-04 19:37       ` Christoph Lameter
2009-11-04 19:44         ` Paul E. McKenney
2009-11-04 10:42     ` Ingo Molnar [this message]
2009-11-05  0:43     ` Rusty Russell
2009-11-04 11:10   ` Ian Campbell
2009-11-04  8:34 ` Rusty Russell

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=20091104104204.GA13194@elte.hu \
    --to=mingo@elte.hu \
    --cc=Ian.Campbell@citrix.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome