From: Nathan Lynch <nathanl@linux.ibm.com>
To: mmc <mmc@linux.vnet.ibm.com>
Cc: ego@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
julietk@linux.ibm.com
Subject: Re: [PATCH] powerpc/rtas: retry when cpu offline races with suspend/migration
Date: Mon, 24 Jun 2019 12:23:40 -0500 [thread overview]
Message-ID: <87h88eucbn.fsf@linux.ibm.com> (raw)
In-Reply-To: <f3b54ef4394bdbf4887d2185bb951c80@linux.vnet.ibm.com>
Hi Mingming,
mmc <mmc@linux.vnet.ibm.com> writes:
> On 2019-06-21 00:05, Nathan Lynch wrote:
>> So return -EAGAIN instead of -EBUSY when this race is
>> encountered. Additionally: logging this event is still appropriate but
>> use pr_info instead of pr_err; and remove use of unlikely() while here
>> as this is not a hot path at all.
>
> Looks good, since it's not a hot path anyway, so unlikely() should
> benefit from optimize compiler path, and should stay. No?
The latency of this path in rtas_ibm_suspend_me() in the best case is
around 2-3 seconds.
So I think not -- this is such a heavyweight and relatively
seldom-executed path that the unlikely() cannot yield any discernible
performance benefit, and its presence imposes a readability cost.
next prev parent reply other threads:[~2019-06-24 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 6:05 [PATCH] powerpc/rtas: retry when cpu offline races with suspend/migration Nathan Lynch
2019-06-24 16:52 ` mmc
2019-06-24 17:23 ` Nathan Lynch [this message]
2019-06-25 1:02 ` Juliet Kim
2019-06-25 18:51 ` Nathan Lynch
2019-06-26 21:40 ` Juliet Kim
2019-06-27 5:01 ` Michael Ellerman
2019-06-27 21:59 ` Juliet Kim
2019-07-01 22:12 ` Nathan Lynch
2019-07-02 2:16 ` Michael Ellerman
2019-07-03 14:27 ` 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=87h88eucbn.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=julietk@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmc@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).