From: Michael Ellerman <mpe@ellerman.id.au>
To: Philippe Bergheaud <felix@linux.vnet.ibm.com>
Cc: Linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: set default kernel thread priority to medium-low
Date: Wed, 11 Dec 2013 17:29:17 +1100 [thread overview]
Message-ID: <1386743357.27999.1.camel@concordia> (raw)
In-Reply-To: <1386661163-4478-1-git-send-email-felix@linux.vnet.ibm.com>
On Tue, 2013-12-10 at 08:39 +0100, Philippe Bergheaud wrote:
> All the important PThread locking occurs in GLIBC libpthread.so
>
> For scaling to large core counts we need to stay out of the kernel and scheduler as much as possible which implies increasing the spin time in user mode. For POWER implementations with SMT this implies that user mode needs to manage SMT priority for spinning and active (in the critical region) threads.
>
> Libpthread must be able to raise and lower the the SMT priority versus the default to be effective.
>
> This lowers the default kernel thread priority from medium to medium-low.
Hi Philippe,
It would be nice if you could make an assertion about what the state of HMT
handling should be once your patch is applied.
I think it's:
* The kernel should use HMT_MEDIUM_LOW as it's "default" priority
* The kernel should use HMT_LOW as it's "low" priority
Which would imply:
* The kernel should not use HMT_MEDIUM anywhere ..
* Nor should it use any of the other higher HMT modes.
Do you agree?
The reason I ask is I still see HMT_MEDIUM used in a few places, and it's not
clear to me if that is correct.
cheers
next prev parent reply other threads:[~2013-12-11 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 7:39 [PATCH] powerpc: set default kernel thread priority to medium-low Philippe Bergheaud
2013-12-11 6:29 ` Michael Ellerman [this message]
2013-12-11 9:49 ` Benjamin Herrenschmidt
2013-12-11 10:30 ` Philippe Bergheaud
2013-12-12 1:22 ` Michael Ellerman
2013-12-12 7:11 ` Philippe Bergheaud
2013-12-13 2:03 ` Michael Ellerman
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=1386743357.27999.1.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=Linuxppc-dev@lists.ozlabs.org \
--cc=felix@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).