From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - Optional method to purge the TLB on SN systems
Date: Tue, 27 Mar 2007 20:33:50 +0000 [thread overview]
Message-ID: <20070327203350.GA20440@sgi.com> (raw)
In-Reply-To: <20070327193925.GA8615@sgi.com>
On Tue, Mar 27, 2007 at 01:24:27PM -0700, Luck, Tony wrote:
> +smp_flush_tlb_cpumask (cpumask_t xcpumask)
> +{
> + unsigned short counts[NR_CPUS];
>
> Even as a "short" ... that is still a lot of stack. Possibly
> a new place to fail when NR_CPUS gets bumped up again?
I was also somwhat concerned about that, too. At NR_CPUS\x1024, it
uses 2k bytes whick is big but I think ok. Even at NR_CPUS 48,
I think is is still ok but I'm getting a little nervous.
FWIW, slab.c has a "struct array_cache *new[NR_CPUS]" on the
stack.
Also, net/core/utils.c has "unsigned long seed[NR_CPUS]".
I'm only adding 1/4 as much space. Can I get away with it or
should I allocate a node-local chunk of memory & keep a pointer to
it in per-cpu data?
>
> +#define IA64_IPI_LOCAL_TLB_FLUSH 0xfc /* SMP reschedule */
> #define IA64_IPI_RESCHEDULE 0xfd /* SMP reschedule */
>
> Cut & pasted the comment when duping this line?
Whoops :-)
Fixed....
next prev parent reply other threads:[~2007-03-27 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 19:39 [PATCH] - Optional method to purge the TLB on SN systems Jack Steiner
2007-03-27 20:24 ` Luck, Tony
2007-03-27 20:33 ` Jack Steiner [this message]
2007-03-27 22:32 ` Luck, Tony
2007-03-27 22:46 ` Jack Steiner
2007-03-28 0:46 ` Zou Nan hai
2007-03-28 1:53 ` Jack Steiner
2007-03-28 3:03 ` Zou, Nanhai
2007-03-28 3:26 ` Jack Steiner
2007-04-05 21:39 ` Jack Steiner
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=20070327203350.GA20440@sgi.com \
--to=steiner@sgi.com \
--cc=linux-ia64@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox