From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Doc: lockdep: add information about performance impact
Date: Tue, 9 Oct 2018 17:43:59 +0200 [thread overview]
Message-ID: <20181009154359.GB5728@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20181009153935eucas1p2dec146575ed5fefd4a0b2b6cb9bac056~b_ujkjRd31303013030eucas1p2C@eucas1p2.samsung.com>
On Tue, Oct 09, 2018 at 05:39:27PM +0200, Lukasz Luba wrote:
> This patch add some warning related to performance drop.
> It should be mentioned that this is not for free
> and the platfrom resources (cache, bus interconnect, etc.)
> will be used more frequently.
To me this reads a bit like: water is wet.
Is this really needed?
next prev parent reply other threads:[~2018-10-09 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181009153935eucas1p2dec146575ed5fefd4a0b2b6cb9bac056@eucas1p2.samsung.com>
2018-10-09 15:39 ` [PATCH] Doc: lockdep: add information about performance impact Lukasz Luba
2018-10-09 15:43 ` Peter Zijlstra [this message]
2018-10-09 15:58 ` Will Deacon
2018-10-10 10:18 ` Russell King - ARM Linux
2018-10-09 16:06 ` Lukasz Luba
2018-10-10 10:31 ` Robin Murphy
2018-10-10 11:49 ` Lukasz Luba
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=20181009154359.GB5728@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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