From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH v6 6/6] locking/lockdep: Reuse freed chain_hlocks entries
Date: Thu, 6 Feb 2020 17:03:34 +0100 [thread overview]
Message-ID: <20200206160334.GV14914@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200206152408.24165-7-longman@redhat.com>
On Thu, Feb 06, 2020 at 10:24:08AM -0500, Waiman Long wrote:
> +#define for_each_chain_block(bucket, prev, curr) \
> + for ((prev) = -1, (curr) = chain_block_buckets[bucket]; \
> + (curr) >= 0; \
> + (prev) = (curr), (curr) = chain_block_next(curr))
> +static inline void add_chain_block(int offset, int size)
> +{
> + int bucket = size_to_bucket(size);
> + int next = chain_block_buckets[bucket];
> + int prev, curr;
> +
> + if (unlikely(size < 2)) {
> + /*
> + * We can't store single entries on the freelist. Leak them.
> + *
> + * One possible way out would be to uniquely mark them, other
> + * than with CHAIN_BLK_FLAG, such that we can recover them when
> + * the block before it is re-added.
> + */
> + if (size)
> + nr_lost_chain_hlocks++;
> + return;
> + }
> +
> + nr_free_chain_hlocks += size;
> + if (!bucket) {
> + nr_large_chain_blocks++;
> +
> + if (unlikely(next >= 0)) {
I was surprised by this condition..
> + /*
> + * Variable sized, sort large to small.
> + */
> + for_each_chain_block(0, prev, curr) {
> + if (size >= chain_block_size(curr))
> + break;
> + }
Because if that is not so, then here:
@curr == @next
@prev == -1
> + init_chain_block(offset, curr, 0, size);
and this will be identical to:
init_chain_block(offset, next, bucket, size);
> + if (prev < 0)
> + chain_block_buckets[0] = offset;
> + else
> + init_chain_block(prev, offset, 0, 0);
and this will be:
chain_block_buckets[bucket] = offset;
Or am I missing something?
> + return;
> + }
> + }
> + /*
> + * Fixed size or bucket[0] empty, add to head.
> + */
> + init_chain_block(offset, next, bucket, size);
> + chain_block_buckets[bucket] = offset;
> +}
next prev parent reply other threads:[~2020-02-06 16:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 15:24 [PATCH v6 0/6] locking/lockdep: Reuse zapped " Waiman Long
2020-02-06 15:24 ` [PATCH v6 1/6] locking/lockdep: Decrement irq context counters when removing lock chain Waiman Long
2020-02-11 12:48 ` [tip: locking/core] locking/lockdep: Decrement IRQ " tip-bot2 for Waiman Long
2020-02-06 15:24 ` [PATCH v6 2/6] locking/lockdep: Display irq_context names in /proc/lockdep_chains Waiman Long
2020-02-11 12:48 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-02-06 15:24 ` [PATCH v6 3/6] locking/lockdep: Track number of zapped classes Waiman Long
2020-02-11 12:48 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-02-06 15:24 ` [PATCH v6 4/6] locking/lockdep: Throw away all lock chains with zapped class Waiman Long
2020-02-11 12:48 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-02-06 15:24 ` [PATCH v6 5/6] locking/lockdep: Track number of zapped lock chains Waiman Long
2020-02-11 12:48 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-02-06 15:24 ` [PATCH v6 6/6] locking/lockdep: Reuse freed chain_hlocks entries Waiman Long
2020-02-06 16:03 ` Peter Zijlstra [this message]
2020-02-06 17:06 ` Waiman Long
2020-02-06 16:16 ` Peter Zijlstra
2020-02-06 17:08 ` Waiman Long
2020-02-06 17:31 ` Peter Zijlstra
2020-02-11 12:48 ` [tip: locking/core] " tip-bot2 for Waiman Long
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=20200206160334.GV14914@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=will.deacon@arm.com \
/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®