All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Doc: lockdep: add information about performance impact
Date: Tue, 9 Oct 2018 16:58:18 +0100	[thread overview]
Message-ID: <20181009155818.GD9259@arm.com> (raw)
In-Reply-To: <20181009154359.GB5728@hirez.programming.kicks-ass.net>

On Tue, Oct 09, 2018 at 05:43:59PM +0200, Peter Zijlstra wrote:
> 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?

I don't think so -- this is a debug option under "kernel hacking". Surely
the perf hit comes with the territory.

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Lukasz Luba <l.luba@partner.samsung.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, b.zolnierkie@samsung.com,
	mingo@redhat.com, corbet@lwn.net
Subject: Re: [PATCH] Doc: lockdep: add information about performance impact
Date: Tue, 9 Oct 2018 16:58:18 +0100	[thread overview]
Message-ID: <20181009155818.GD9259@arm.com> (raw)
In-Reply-To: <20181009154359.GB5728@hirez.programming.kicks-ass.net>

On Tue, Oct 09, 2018 at 05:43:59PM +0200, Peter Zijlstra wrote:
> 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?

I don't think so -- this is a debug option under "kernel hacking". Surely
the perf hit comes with the territory.

Will

  reply	other threads:[~2018-10-09 15:58 UTC|newest]

Thread overview: 14+ 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:39   ` Lukasz Luba
2018-10-09 15:43   ` Peter Zijlstra
2018-10-09 15:43     ` Peter Zijlstra
2018-10-09 15:58     ` Will Deacon [this message]
2018-10-09 15:58       ` Will Deacon
2018-10-10 10:18       ` Russell King - ARM Linux
2018-10-10 10:18         ` Russell King - ARM Linux
2018-10-09 16:06     ` Lukasz Luba
2018-10-09 16:06       ` Lukasz Luba
2018-10-10 10:31       ` Robin Murphy
2018-10-10 10:31         ` Robin Murphy
2018-10-10 11:49         ` Lukasz Luba
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=20181009155818.GD9259@arm.com \
    --to=will.deacon@arm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.