From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [x86] d55564cfc2: will-it-scale.per_thread_ops -5.8% regression
Date: Fri, 08 Jan 2021 10:51:56 +0100 [thread overview]
Message-ID: <X/grPFTgOMvtqEVZ@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <824461ae2cb642b1b2f82fac140a98da@AcuMS.aculab.com>
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
On Fri, Jan 08, 2021 at 09:37:45AM +0000, David Laight wrote:
> The lack of spinlocks in userspace really kills you.
Glibc has them, but please don't complain about lock holder preemption
issues if you do actually use them ;-)
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: David Laight <David.Laight@aculab.com>
Cc: 'Linus Torvalds' <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
kernel test robot <oliver.sang@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
"lkp@lists.01.org" <lkp@lists.01.org>,
kernel test robot <lkp@intel.com>,
"Huang, Ying" <ying.huang@intel.com>,
Feng Tang <feng.tang@intel.com>,
"zhengjun.xing@intel.com" <zhengjun.xing@intel.com>
Subject: Re: [x86] d55564cfc2: will-it-scale.per_thread_ops -5.8% regression
Date: Fri, 8 Jan 2021 10:51:56 +0100 [thread overview]
Message-ID: <X/grPFTgOMvtqEVZ@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <824461ae2cb642b1b2f82fac140a98da@AcuMS.aculab.com>
On Fri, Jan 08, 2021 at 09:37:45AM +0000, David Laight wrote:
> The lack of spinlocks in userspace really kills you.
Glibc has them, but please don't complain about lock holder preemption
issues if you do actually use them ;-)
next prev parent reply other threads:[~2021-01-08 9:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 13:47 [x86] d55564cfc2: will-it-scale.per_thread_ops -5.8% regression kernel test robot
2021-01-07 13:47 ` kernel test robot
2021-01-07 17:43 ` Linus Torvalds
2021-01-07 17:43 ` Linus Torvalds
2021-01-07 18:33 ` Al Viro
2021-01-07 18:33 ` Al Viro
2021-01-07 18:40 ` Al Viro
2021-01-07 18:40 ` Al Viro
2021-01-07 18:55 ` Al Viro
2021-01-07 18:55 ` Al Viro
2021-01-07 18:47 ` Linus Torvalds
2021-01-07 18:47 ` Linus Torvalds
2021-01-07 18:58 ` Al Viro
2021-01-07 18:58 ` Al Viro
2021-01-07 19:04 ` Al Viro
2021-01-07 19:04 ` Al Viro
2021-01-07 19:33 ` Linus Torvalds
2021-01-07 19:33 ` Linus Torvalds
2021-01-07 19:57 ` Al Viro
2021-01-07 19:57 ` Al Viro
2021-01-08 9:29 ` David Laight
2021-01-08 9:29 ` David Laight
2021-01-08 9:37 ` David Laight
2021-01-08 9:37 ` David Laight
2021-01-08 9:51 ` Peter Zijlstra [this message]
2021-01-08 9:51 ` Peter Zijlstra
2021-01-08 10:44 ` David Laight
2021-01-08 10:44 ` David Laight
2021-01-08 9:49 ` David Laight
2021-01-08 9:49 ` David Laight
2021-01-08 6:13 ` Oliver Sang
2021-01-08 6:13 ` Oliver Sang
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=X/grPFTgOMvtqEVZ@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=lkp@lists.01.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.