From: Lukasz Luba <lukasz.luba@arm.com>
To: Markus Elfring <Markus.Elfring@web.de>,
Bernard Zhao <bernard@vivo.com>,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, opensource.kernel@vivo.com,
Krzysztof Kozlowski <krzk@kernel.org>,
Kukjin Kim <kgene@kernel.org>
Subject: Re: [v2] memory/samsung: reduce unnecessary mutex lock area
Date: Tue, 12 May 2020 13:48:23 +0100 [thread overview]
Message-ID: <113c5695-5415-03f2-c99a-b394b3118d33@arm.com> (raw)
In-Reply-To: <5a12fa12-f4e0-c941-b22b-33436723b44e@web.de>
On 5/12/20 1:32 PM, Markus Elfring wrote:
>> Something like: 'memory/samsung: reduce protected code area in IRQ
>> handler' for the subject header would be better.
>> Then in the message explain (without 'maybe') that it will speed-up a
>> bit this IRQ processing and there is no need to protect return value
>> or printing.
>
> Do you tend to prefer smaller lock scopes for nicer run time characteristics?
Yes and I am probably not the only one. Of course it consumes time, to
make and test this kind of changes (so it must be in my current scope
of work).
Regards,
Lukasz
>
> Regards,
> Markus
>
prev parent reply other threads:[~2020-05-12 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 11:40 [PATCH v2] memory/samsung: reduce unnecessary mutex lock area Markus Elfring
2020-05-12 11:56 ` Lukasz Luba
2020-05-12 12:31 ` Bernard
2020-05-12 12:32 ` [v2] " Markus Elfring
2020-05-12 12:48 ` Lukasz Luba [this message]
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=113c5695-5415-03f2-c99a-b394b3118d33@arm.com \
--to=lukasz.luba@arm.com \
--cc=Markus.Elfring@web.de \
--cc=bernard@vivo.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=opensource.kernel@vivo.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