mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Vlad Poenaru <vlad.wing@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Boqun Feng <boqun@kernel.org>, Waiman Long <longman@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Eric Dumazet <edumazet@kernel.org>,
	Davide Caratti <dcaratti@redhat.com>,
	Breno Leitao <leitao@debian.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] lockdep: Keep dynamic key hash nodes in lockdep-owned storage
Date: Wed, 21 Oct 2026 20:01:56 -0700	[thread overview]
Message-ID: <ef57e0ab-f0b4-46d6-a2f8-f6c97fec8d8e@acm.org> (raw)
In-Reply-To: <20261021115621.3194947-1-vlad.wing@gmail.com>

On 10/21/26 4:56 AM, Vlad Poenaru wrote:
>   #define MAX_LOCKDEP_ENTRIES	16384UL
>   #define MAX_LOCKDEP_CHAINS_BITS	15
> +#define MAX_LOCKDEP_DYNAMIC_KEYS	1024UL
>   #define MAX_STACK_TRACE_ENTRIES	262144UL
>   #define STACK_TRACE_HASH_SIZE	8192

This patch introduces a new hard upper limit on the number of dynamic
lockdep keys. That's unfortunate but I assume it's not possible to
eliminate this hard upper bound if the key storage is owned by
lockdep?

Thanks,

Bart.

  reply	other threads:[~2026-10-22  3:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 11:56 Vlad Poenaru
2026-10-22  3:01 ` Bart Van Assche [this message]
2026-10-23 12:19   ` Vlad Poenaru
2026-10-26 14:07     ` Boqun Feng
2026-10-28 11:44       ` Vlad Poenaru
2026-10-28 14:21         ` Davide Caratti

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=ef57e0ab-f0b4-46d6-a2f8-f6c97fec8d8e@acm.org \
    --to=bvanassche@acm.org \
    --cc=akpm@linux-foundation.org \
    --cc=boqun@kernel.org \
    --cc=dcaratti@redhat.com \
    --cc=edumazet@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=vlad.wing@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
all inboxes | Powered by JetHome®