From: Pavel Machek <pavel@ucw.cz>
To: Mike Galbraith <efault@gmx.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
kernel list <linux-kernel@vger.kernel.org>,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
peterz@infradead.org
Subject: Re: niced tasks on SMT system
Date: Thu, 28 Dec 2017 19:53:54 +0100 [thread overview]
Message-ID: <20171228185354.GA3631@amd> (raw)
In-Reply-To: <1514467413.6886.35.camel@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2523 bytes --]
Hi!
> > Ok, so I'm compiling, and I'd like to run a flight simulator.
> >
> > Flightgear normally does 20fps on my system... kinda low but playable.
> >
> > I have reniced make -j 5 fo kernel running. Scheduler gives 100% of
> > one of CPUs to Flightgear (good), but the smt sibling is used by the
> > compilation, and I'm down to 9 fps. Not good.
> >
> > Even with single-threaded make, I have 10-13fps.
> >
> > Is there way to learn which CPUs are SMT siblings?
>
> cat /sys/devices/system/cpu/cpu{N}/topology/thread_siblings
Thanks for a hint.
Well, something is definitely wrong there:
pavel@duo:/data/l/linux-n900$ cat
/sys/devices/system/cpu/cpu0/topology/thread_siblings
03
I believe that means that cpu0 & cpu1 are sharing physical cpu. Yet,
when I run flightgear and "nice while1". flightgear goes to CPU#0 and
while1 to CPU#1. Would not it be nice if while1 went preferably to
CPUs #2 and #3? Ok. after a while while1 moved to cpu#2, good.
> > Is there way to disable SMT during runtime?
>
> You could offline them, but wouldn't it be better to tell each which
> CPUs they can use, or perhaps partition your box with cpusets?
Let me try offlining first... and yes, SMT seems to be problem here.
| CPU0 | CPU1 | CPU2 | CPU3 | |
| flightgear | off | off | off | 21 fps |
| flightgear | while1 | off | off | 17 fps |
| flightgear+while1 | off | off | off | 10 fps |
| flightgear | off | while1 | off | 21 fps |
> > Can I do something to improve Flightgear performance and still do
> > compilation?
>
> Sure, run everything associated with your game as RT, and everything
> not game gets the leftover cycles. If there are none, box will
> throttle RT to save itself from it's psycho :) driver and you'll know
> that you need a bigger box. (it's likely your phone)
> Oh yeah, echo NO_RT_RUNTIME_SHARE > /sys/kernel/debug/sched_features
> before you try that, otherwise the throttle won't help.
Sure, but that is not a problem I have.
Scheduler already (correctly) decides that the game is important, and
gives game all the time it wants (100% of one CPU). That is not a problem.
Problem seems to be that it schedules other tasks to SMT sibling, and
that slows down the game quite significantly.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-12-28 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 12:10 niced tasks on SMT system Pavel Machek
2017-12-28 13:23 ` Mike Galbraith
2017-12-28 18:53 ` Pavel Machek [this message]
2017-12-28 18:58 ` Ozgur
2017-12-28 20:59 ` Pavel Machek
2017-12-28 21:07 ` Ozgur
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=20171228185354.GA3631@amd \
--to=pavel@ucw.cz \
--cc=efault@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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