From: Babu Moger <babu.moger@oracle.com>
To: peterz@infradead.org, mingo@redhat.com,
akpm@linux-foundation.org, keescook@chromium.org,
dan.j.williams@intel.com, aryabinin@virtuozzo.com, tj@kernel.org
Cc: linux-kernel@vger.kernel.org, babu.moger@oracle.com
Subject: [PATCH 0/2] Ajust lockdep static allocations
Date: Thu, 22 Sep 2016 11:43:34 -0700 [thread overview]
Message-ID: <1474569816-170269-1-git-send-email-babu.moger@oracle.com> (raw)
These patches adjust the static allocations for lockdep
data structures used for debugging locking correctness. The current
code reserves about 4MB extra space for these data structures. Most
of the configurations do not need these many data structures. While
testing, I have not seen it go beyond 20% of already reserved entries.
$grep "lock-classes" /proc/lockdep_stats
lock-classes: 1560 [max: 8191]
Reserving even more space seems unreasonable. So, keeping the default
entries small as before the Commit 1413c0389333 ("lockdep: Increase static
allocations"). Added new CONFIG_PROVE_LOCKING_PLUS in case someone
needs more entries to debug their large configuration.
Patch 1 : Adjusts the sizes based on the new config parameter
patch 2 : Adds new config parameter
Babu Moger (2):
lockdep: Keep the default static allocations small
config: Add new CONFIG_PROVE_LOCKING_PLUS
kernel/locking/lockdep_internals.h | 14 +++++++++++---
lib/Kconfig.debug | 10 ++++++++++
2 files changed, 21 insertions(+), 3 deletions(-)
next reply other threads:[~2016-09-22 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 18:43 Babu Moger [this message]
2016-09-22 18:43 ` [PATCH 1/2] lockdep: Keep the default static allocations small Babu Moger
2016-09-22 18:43 ` [PATCH 2/2] config: Add new CONFIG_PROVE_LOCKING_PLUS Babu Moger
2016-09-23 7:12 ` [PATCH 0/2] Ajust lockdep static allocations Peter Zijlstra
2016-09-23 14:04 ` Babu Moger
2016-09-23 14:34 ` Peter Zijlstra
2016-09-23 14:50 ` Babu Moger
2016-09-23 15:04 ` Peter Zijlstra
2016-09-23 15:15 ` Babu Moger
2016-09-23 15:40 ` Peter Zijlstra
2016-09-23 19:57 ` Babu Moger
2016-09-23 20:08 ` Rob Gardner
2016-09-23 20:17 ` Peter Zijlstra
2016-09-23 20:30 ` Babu Moger
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=1474569816-170269-1-git-send-email-babu.moger@oracle.com \
--to=babu.moger@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dan.j.williams@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®