From: Andi Kleen <andi@firstfloor.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Dave Kleikamp <dkleikamp@gmail.com>,
Chris Mason <chris.mason@oracle.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Tim Chen <tim.c.chen@linux.intel.com>,
linux-kernel@vger.kernel.org, lenb@kernel.org,
paulmck@us.ibm.com
Subject: Re: idle issues running sembench on 128 cpus
Date: Wed, 04 May 2011 16:49:42 -0700 [thread overview]
Message-ID: <m2liymyqjt.fsf@firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.2.02.1105050144030.3005@ionos> (Thomas Gleixner's message of "Thu, 5 May 2011 01:47:44 +0200 (CEST)")
Thomas Gleixner <tglx@linutronix.de> writes:
> On Thu, 5 May 2011, Andi Kleen wrote:
>> On Thu, May 05, 2011 at 01:29:49AM +0200, Thomas Gleixner wrote:
>> > That makes sense, but merging the timeouts race free will be a real
>> > PITA.
>>
>> For this case one could actually use a spinlock between the siblings.
>> That shouldn't be a problem as long as it's not a global spinlock.
>
> Care to give it a try ?
Ok, will try tomorrow.
>> Here's a new patch without the raw. Boots on my Westmere.
>
>> + cpu = raw_smp_processor_id();
>
> Hmm. quilt refresh perhaps ? I know that feeling :)
The scp to copy the patch was too slow. Noticed it later and sent a new
one.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2011-05-04 23:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 21:47 idle issues running sembench on 128 cpus Dave Kleikamp
2011-05-04 22:04 ` Thomas Gleixner
2011-05-04 22:07 ` Andi Kleen
2011-05-04 22:34 ` Thomas Gleixner
2011-05-04 23:03 ` Andi Kleen
2011-05-04 23:29 ` Thomas Gleixner
2011-05-04 23:42 ` Andi Kleen
2011-05-04 23:47 ` Thomas Gleixner
2011-05-04 23:49 ` Andi Kleen [this message]
2011-05-04 23:51 ` Thomas Gleixner
2011-05-04 23:48 ` idle issues running sembench on 128 cpus II Andi Kleen
2011-05-05 15:24 ` Dave Kleikamp
2011-05-05 13:58 ` idle issues running sembench on 128 cpus Thomas Gleixner
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=m2liymyqjt.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=chris.mason@oracle.com \
--cc=dkleikamp@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.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 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.