Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210711141430.896595-1-sxwjean@me.com> <20210711141430.896595-3-sxwjean@me.com>
 <93ccb871-7f57-9109-9072-8fc26f3b811c@redhat.com>
In-Reply-To: <93ccb871-7f57-9109-9072-8fc26f3b811c@redhat.com>
From:   Xiongwei Song <sxwjean@gmail.com>
Date:   Mon, 12 Jul 2021 15:49:12 +0800
Message-ID: <CAEVVKH-yQgFi2U4v2p4mN_aaUM7=A8UEpSK67wUpacpc-MtFAw@mail.gmail.com>
Subject: Re: [PATCH v1 3/3] locking/lockdep,doc: Correct the max number of
 lock classes
To:     Waiman Long <llong@redhat.com>
Cc:     Xiongwei Song <sxwjean@me.com>, peterz@infradead.org,
        mingo@redhat.com, will@kernel.org,
        Boqun Feng <boqun.feng@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sun, Jul 11, 2021 at 11:22 PM Waiman Long <llong@redhat.com> wrote:
>
> On 7/11/21 10:14 AM, Xiongwei Song wrote:
> > 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
>
> Acked-by: Waiman Long <longman@redhat.com>

Thanks.