From: Peter Zijlstra <peterz@infradead.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] lockdep: do not count lock class operations without CONFIG_DEBUG_LOCKDEP
Date: Fri, 19 May 2017 11:09:10 +0200 [thread overview]
Message-ID: <20170519090910.fubv3c3ozfckavi3@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <149517756125.33116.15222517572640587072.stgit@buzz>
On Fri, May 19, 2017 at 10:06:01AM +0300, Konstantin Khlebnikov wrote:
> Currently this counter shown in /proc/lockdep if CONFIG_DEBUG_LOCKDEP=y
> This patch disables it completely if this option is disabled.
>
> This counter might be useful for debugging lockdep itself, but for normal
> debugging it seems useless. Lockstat provides more detailed statistics.
>
> This atomic_inc is a hot spot inside __lock_acquire() for debug kernel.
>
> With patch "netperf -H localhost" shows some boost: 2500 -> 2600
Nothing against these patches, but I do wonder why you're performance
optimizing debug kernels ;-)
next prev parent reply other threads:[~2017-05-19 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 7:06 Konstantin Khlebnikov
2017-05-19 9:09 ` Peter Zijlstra [this message]
2017-05-19 9:28 ` Konstantin Khlebnikov
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=20170519090910.fubv3c3ozfckavi3@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®