From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Travis <travis@sgi.com>,
anton@samba.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Finishing off cpumask...
Date: Thu, 21 Oct 2010 17:35:23 +1030 [thread overview]
Message-ID: <201010211735.23918.rusty@rustcorp.com.au> (raw)
I have had five final cpumask patches in my queue for over a year now, and
I'd like to merge them *next* merge window (not this one, too late).
The first two finally convert mm_struct and task_struct to variable cpumasks,
which are the last in the core kernel. The next two turn off and break
old-style cpumask uses when CONFIG_CPUMASK_OFFSTACK is set, and the final one
actually means we don't allocate all NR_CPUS bits for bitmasks.
Historically, this stuff has revealed issues when turned on, so I'd like it
to have a long baking cycle in Ingo's tree and big-machine testers.
I'm rebasing and retesting now, will post git tree when I have it.
Thanks,
Rusty.
next reply other threads:[~2010-10-21 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 7:05 Rusty Russell [this message]
2010-10-21 9:21 ` Finishing off cpumask Peter Zijlstra
2010-10-22 0:02 ` 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=201010211735.23918.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=travis@sgi.com \
--cc=x86@kernel.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 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.