From: Michael Ellerman <mpe@ellerman•id.au>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
linuxppc-dev@lists•ozlabs.org
Cc: mikey@neuling•org
Subject: Re: powerpc/opal: Wake up kopald polling thread before waiting for events
Date: Mon, 4 Jul 2016 16:11:10 +1000 (AEST) [thread overview]
Message-ID: <3rjc8Z6nDPz9sXx@ozlabs.org> (raw)
In-Reply-To: <1467607904.13965.1.camel@kernel.crashing.org>
On Mon, 2016-04-07 at 04:51:44 UTC, Benjamin Herrenschmidt wrote:
> On some environments (prototype machines, some simulators, etc...)
> there is no functional interrupt source to signal completion, so
> we rely on the fairly slow OPAL heartbeat.
>
> In a number of cases, the calls complete very quickly or even
> immediately. We've observed that it helps a lot to wakeup the OPAL
> heartbeat thread before waiting for event in those cases, it will
> call OPAL immediately to collect completions for anything that
> finished fast enough.
Any performance/jitter impact on normal systems?
cheers
next prev parent reply other threads:[~2016-07-04 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 4:51 [PATCH] powerpc/opal: Wake up kopald polling thread before waiting for events Benjamin Herrenschmidt
2016-07-04 6:11 ` Michael Ellerman [this message]
2016-07-04 7:50 ` Benjamin Herrenschmidt
2016-07-04 9:45 ` [PATCH] " Michael Neuling
2016-07-11 10:19 ` 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=3rjc8Z6nDPz9sXx@ozlabs.org \
--to=mpe@ellerman$(echo .)id.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mikey@neuling$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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