From: Xiongwei Song <sxwjean@me.com>
To: peterz@infradead.org, mingo@redhat.com, will@kernel.org,
longman@redhat.com, boqun.feng@gmail.com
Cc: linux-kernel@vger.kernel.org, Xiongwei Song <sxwjean@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [PATCH v1 3/3] locking/lockdep,doc: Correct the max number of lock classes
Date: Sun, 11 Jul 2021 22:14:30 +0800 [thread overview]
Message-ID: <20210711141430.896595-3-sxwjean@me.com> (raw)
In-Reply-To: <20210711141430.896595-1-sxwjean@me.com>
From: Xiongwei Song <sxwjean@gmail.com>
The max number of lock classes is 8192.
Signed-off-by: Xiongwei Song <sxwjean@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
Documentation/locking/lockdep-design.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/locking/lockdep-design.rst b/Documentation/locking/lockdep-design.rst
index 82f36cab61bd..5c2dcec684ff 100644
--- a/Documentation/locking/lockdep-design.rst
+++ b/Documentation/locking/lockdep-design.rst
@@ -341,7 +341,7 @@ Exceeding this number will trigger the following lockdep warning::
(DEBUG_LOCKS_WARN_ON(id >= MAX_LOCKDEP_KEYS))
-By default, MAX_LOCKDEP_KEYS is currently set to 8191, and typical
+By default, MAX_LOCKDEP_KEYS is currently set to 8192, and typical
desktop systems have less than 1,000 lock classes, so this warning
normally results from lock-class leakage or failure to properly
initialize locks. These two problems are illustrated below:
@@ -383,7 +383,7 @@ you the number of lock classes currently in use along with the maximum::
This command produces the following output on a modest system::
- lock-classes: 748 [max: 8191]
+ lock-classes: 748 [max: 8192]
If the number allocated (748 above) increases continually over time,
then there is likely a leak. The following command can be used to
--
2.30.2
next prev parent reply other threads:[~2021-07-11 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 14:14 [RFC PATCH v1 1/3] locking/lockdep: Fix false warning of check_wait_context() Xiongwei Song
2021-07-11 14:14 ` [RFC PATCH v1 2/3] locking/lockdep: Unify the return values " Xiongwei Song
2021-07-11 15:19 ` Waiman Long
2021-07-12 7:48 ` Xiongwei Song
2021-07-23 2:57 ` [locking/lockdep] e0a77a7a5a: WARNING:bad_unlock_balance_detected kernel test robot
2021-07-11 14:14 ` Xiongwei Song [this message]
2021-07-11 15:22 ` [PATCH v1 3/3] locking/lockdep,doc: Correct the max number of lock classes Waiman Long
2021-07-12 7:49 ` Xiongwei Song
2021-07-11 16:43 ` [RFC PATCH v1 1/3] locking/lockdep: Fix false warning of check_wait_context() Waiman Long
2021-07-12 8:18 ` Xiongwei Song
2021-07-12 8:50 ` Boqun Feng
2021-07-12 9:21 ` Xiongwei Song
2021-07-12 13:04 ` Waiman Long
2021-07-12 15:03 ` Xiongwei Song
2021-07-13 2:29 ` Xiongwei Song
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=20210711141430.896595-3-sxwjean@me.com \
--to=sxwjean@me.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sxwjean@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).