From: Rusty Russell <rusty@rustcorp.com.au>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
npiggin@suse.de, axboe@kernel.dk
Subject: Re: [PATCH 1/1] cpumask: smp_call_function_many()
Date: Thu, 20 Nov 2008 21:38:04 +1030 [thread overview]
Message-ID: <200811202138.05232.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200811201757.07726.nickpiggin@yahoo.com.au>
On Thursday 20 November 2008 17:27:07 Nick Piggin wrote:
> On Thursday 20 November 2008 15:44, Rusty Russell wrote:
> > I can prepare a separate patch which just changes this over, rather than
> > doing it as part of the smp_call_function_many() conversion, but I
> > couldn't stomach touching that quiescing code :(
>
> What's wrong with it? It's well commented and I would have thought pretty
> simple. A bit ugly, but straightforward. I still don't really see why it
> needs changing.
Ah, sorry if I was unclear. The point of this 150+ patch series is to get
cpumasks off the stack.
Here's the problem:
struct call_function_data {
struct call_single_data csd;
spinlock_t lock;
unsigned int refs;
cpumask_t cpumask;
struct rcu_head rcu_head;
};
...
static void smp_call_function_mask_quiesce_stack(cpumask_t mask)
{
struct call_single_data data;
...
So, it's far simpler just to fix the code to do the "dumb" thing.
Rusty.
next prev parent reply other threads:[~2008-11-20 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 14:45 [PATCH 1/1] cpumask: smp_call_function_many() Rusty Russell
2008-11-19 20:23 ` Hiroshi Shimamoto
2008-11-19 23:38 ` Rusty Russell
2008-11-20 3:21 ` Nick Piggin
2008-11-20 4:44 ` Rusty Russell
2008-11-20 6:57 ` Nick Piggin
2008-11-20 11:08 ` Rusty Russell [this message]
2008-11-20 11:12 ` Nick Piggin
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=200811202138.05232.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=axboe@kernel.dk \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=npiggin@suse.de \
--cc=schwidefsky@de.ibm.com \
--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