All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, anton@samba.org,
	Mike Travis <travis@sgi.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PULL] cpumask offstack finalization
Date: Fri, 11 Feb 2011 08:02:17 +1030	[thread overview]
Message-ID: <201102110802.17453.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20110210124416.GE26094@elte.hu>

On Thu, 10 Feb 2011 11:14:16 pm Ingo Molnar wrote:
> 
> * Rusty Russell <rusty@rustcorp.com.au> wrote:
> 
> > Hi Ingo,
> > 
> >    A few more obsolete uses of cpumask has crept into the tree; all easily
> > fixed.  This is rebased onto your -tip tree and re-tested; it finally means
> > that we can detect obsolescent (and hence dangerous) cpumask usage when 
> > CONFIG_CPUMASK_OFFSTACK=y.  It finally reduces the actual allocation of
> > cpumask_var_t to the number of cpus we actually have.
> 
> Hm, could we get rid of the obsolete percpu APIs once and for all? The fact that 
> they are still around cause the leakage into new code to begin with.

Yes; it'll be a fair bit of arch churn, but it can be done in stages easily.
I thought about marking them all __deprecated but that just annoys people.

And yes, this is definitely .39+.

Thanks,
Rusty.

  parent reply	other threads:[~2011-02-10 21:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  5:38 [PULL] cpumask offstack finalization Rusty Russell
2011-02-10 12:44 ` Ingo Molnar
2011-02-10 19:29   ` Linus Torvalds
2011-02-10 21:18     ` Ingo Molnar
2011-02-10 21:32   ` Rusty Russell [this message]
2011-02-10 22:13     ` Thomas Gleixner
2011-02-10 23:51       ` Linus Torvalds
2011-02-10 23:59         ` Ingo Molnar
2011-02-11 13:41           ` Alexey Dobriyan
2011-02-11 14:07             ` Ingo Molnar
2011-02-11 13:44         ` Alexey Dobriyan

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=201102110802.17453.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=travis@sgi.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 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.