public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-kernel@vger.kernel.org, linux-bcachefs@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>
Subject: Re: [PATCH] lockdep: lockdep_set_notrack_class()
Date: Sun, 30 Jun 2024 23:16:36 -0400	[thread overview]
Message-ID: <62c553f2-2fb3-4b83-86ae-5b038941cdbb@redhat.com> (raw)
In-Reply-To: <uvf4ilncakodvwmu6kbzs4lrxgeegtanhyhsk52xj7foil65jm@p54wibff6bgc>


On 6/30/24 20:10, Kent Overstreet wrote:
> On Sun, Jun 30, 2024 at 06:08:21PM GMT, Waiman Long wrote:
>> On 6/30/24 01:10, Kent Overstreet wrote:
>>> Add a new helper to disable lockdep tracking entirely for a given class.
>>>
>>> This is needed for bcachefs, which takes too many btree node locks for
>>> lockdep to track. Instead, we have a single lockdep_map for "btree_trans
>>> has any btree nodes locked", which makes more since given that we have
>>> centralized lock management and a cycle detector.
>> Could you explain a bit more what the current novalidate_class is lacking
>> WRT to the bcachefs lock? Is it excessive performance overhead or some bogus
>> lockdep warning?
> novalidate just switches off checking of lock ordering, but the fact
> that the locks are held is still tracked.
>
> bcachefs takes more btree node locks than lockdep can track, so I'm
> switching to a single lockdep map for "this btree_trans has any btree
> nodes locked" instead.

I asked because you are adding a new special class that is similar to 
no_validate in some way but also a bit different. So we need to document 
what each of these special classes are for to avoid confusion.

Cheers,
Longman


      reply	other threads:[~2024-07-01  3:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30  5:10 [PATCH] lockdep: lockdep_set_notrack_class() Kent Overstreet
2024-06-30 22:08 ` Waiman Long
2024-07-01  0:10   ` Kent Overstreet
2024-07-01  3:16     ` Waiman Long [this message]

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=62c553f2-2fb3-4b83-86ae-5b038941cdbb@redhat.com \
    --to=longman@redhat.com \
    --cc=boqun.feng@gmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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