public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-arch@vger.kernel.org
Cc: Mike Travis <travis@sgi.com>
Subject: Heads up: cpumask changes
Date: Wed, 19 Nov 2008 00:30:10 +1030	[thread overview]
Message-ID: <200811190030.10550.rusty@rustcorp.com.au> (raw)

Hi all,

   With large NR_CPUS coming, Mike and I have been working to make dynamic 
cpumasks an option.  The main change is to APIs which pass cpumask_t around; 
they'll now be '[const] struct cpumask *'.  This unfortunately will hit arch 
code as interfaces get frobbed, and a couple of nasty one-shot transitions are 
unavoidable.

   For archs which never intend to support CONFIG_CPUMASK_OFFSTACK, the rest 
of the changes will be cosmetic (eg. s/cpumask_t/struct cpumask/ eventually).  
For x86 and others who allow CONFIG_CPUMASK_OFFSTACK, "struct cpumask" will 
eventually be undefined so it cannot be assigned or used on the stack: this 
means use cpumask_copy(), cpumask_var_t and as a last resort, 
DEFINE_BITMAP(bitmap, NR_CPUS) and to_cpumask(bitmap).

   We've been working most closely with Ingo, as x86, irq and scheduler are 
most effected.  Apologies in advance for the churn, but the final result will 
be a neater API than what we have now as well as stupid numbers of cpus in 
your .config.

Thanks!
Rusty.

                 reply	other threads:[~2008-11-18 14:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200811190030.10550.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-arch@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox