public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Mike Travis <travis@sgi.com>
Subject: [PATCH 0/6] Final cpumask conversion patches for 4096+ cpus
Date: Thu, 19 Nov 2009 19:28:37 +1030	[thread overview]
Message-ID: <200911191928.38048.rusty@rustcorp.com.au> (raw)

Finally, these 6 patches actually allocate short (nr_cpu_ids-bits) cpumasks
and nail down the lid so the compiler will find new abuses if they creep in.

For non-CONFIG_CPUMASK_OFFSTACK:
   The only visible changes are that you have to use the accessors
   mm_cpumask() and tsk_cpumask.  They convert the bitmaps (moved to the end
   of those structs) to 'struct cpumask *'.

For CONFIG_CPUMASK_OFFSTACK=y:
   We allocate the mm and task_struct bitmaps short (nr_cpu_ids, rather
   than the compile-time NR_CPUS).  A couple of patches get rid of the
   old-style cpus_ ops so noone uses them accidentally.  We don't define
   struct cpumask at all, which prevents accidental abuse.  Finally, we
   reduce cpumask_size() so our dynamically-allocated cpumasks are only
   nr_cpu_ids big.

Cheers,
Rusty.

                 reply	other threads:[~2009-11-19  8:58 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=200911191928.38048.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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