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 v5 7/7] locking/lockdep: Add a fast path for chain_hlocks allocation
Date: Tue, 4 Feb 2020 14:44:46 +0100 [thread overview]
Message-ID: <20200204134446.GQ14946@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200204131813.GQ14914@hirez.programming.kicks-ass.net>
On Tue, Feb 04, 2020 at 02:18:13PM +0100, Peter Zijlstra wrote:
> On Mon, Feb 03, 2020 at 11:41:47AM -0500, Waiman Long wrote:
>
> > @@ -2809,6 +2813,18 @@ static int alloc_chain_hlocks(int req)
> > return curr;
> > }
> >
> > + /*
> > + * Fast path: splitting out a sub-block at the end of the
> > + * primordial chain block.
> > + */
> > + if (likely((size > MAX_LOCK_DEPTH) &&
> > + (size - req > MAX_CHAIN_BUCKETS))) {
> > + size -= req;
> > + nr_free_chain_hlocks -= req;
> > + init_chain_block_size(curr, size);
> > + return curr + size;
> > + }
> > +
> > if (size > max_size) {
> > max_prev = prev;
> > max_curr = curr;
>
> A less horrible hack might be to keep the freelist sorted on size (large
> -> small)
>
> That moves the linear-search from alloc_chain_hlocks() into
> add_chain_block(). But the thing is that it would amortize to O(1)
> because this initial chunk is pretty much 'always' the largest.
>
> Only once we've exhausted the initial block will we hit that search, but
> then the hope is that we mostly live off of the buckets, not the
> variable freelist.
Completely untested something like so
---
--- a/kernel/locking/lockdep.c
+++ b/kernel/locking/lockdep.c
@@ -2717,7 +2717,7 @@ static inline void init_chain_block(int
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, next = chain_block_buckets[bucket];
if (unlikely(size < 2)) {
/*
@@ -2731,26 +2731,38 @@ static inline void add_chain_block(int o
return;
}
- init_chain_block(offset, next, bucket, size);
- chain_block_buckets[bucket] = offset;
- nr_free_chain_hlocks += size;
-
- if (bucket == 0)
+ if (!bucket) {
nr_large_chain_blocks++;
+ /*
+ * Variable sized, sort large to small.
+ */
+ for_each_chain_block(0, prev, curr, next) {
+ if (size > chain_block_size(curr))
+ break;
+ }
+ init_chain_block(offset, curr, 0, size);
+ if (prev < 0)
+ chain_block_buckets[prev + MAX_CHAIN_BUCKETS] = offset;
+ else
+ init_chain_block(prev, offset, MAX_CHAIN_BUCKETS, 0);
+ } else {
+ /*
+ * Fixed size, add to head.
+ */
+ init_chain_block(offset, next, bucket, size);
+ chain_block_buckets[bucket] = offset;
+ }
+ nr_free_chain_hlocks += size;
}
+
/*
* When offset < 0, the bucket number is encoded in it.
*/
-static inline void del_chain_block(int offset, int size, int next)
+static inline void del_chain_block(int bucket, int size, int next)
{
- int bucket = size_to_bucket(size);
-
nr_free_chain_hlocks -= size;
- if (offset < 0)
- chain_block_buckets[offset + MAX_CHAIN_BUCKETS] = next;
- else
- init_chain_block(offset, next, bucket, size);
+ chain_block_buckets[bucket] = next;
if (bucket == 0)
nr_large_chain_blocks--;
@@ -2774,9 +2786,7 @@ static void init_chain_block_buckets(voi
*/
static int alloc_chain_hlocks(int req)
{
- int max_prev, max_curr, max_next, max_size = INT_MIN;
- int prev, curr, next, size;
- int bucket;
+ int bucket, curr, size;
/*
* We rely on the MSB to act as an escape bit to denote freelist
@@ -2798,40 +2808,24 @@ static int alloc_chain_hlocks(int req)
if (bucket != 0) {
curr = chain_block_buckets[bucket];
- if (curr < 0)
- goto search;
-
- del_chain_block(bucket - MAX_CHAIN_BUCKETS, req,
- chain_block_next(curr));
- return curr;
+ if (curr >= 0) {
+ del_chain_block(bucket, req, chain_block_next(curr));
+ return curr;
+ }
}
-search:
/*
- * linear search of the variable sized freelist; look for an exact
- * match or the largest block.
+ * The variable sized freelist is sorted by size; the first entry is
+ * the largest. Use it if it fits.
*/
- for_each_chain_block(0, prev, curr, next) {
+ curr = chain_block_buckets[0];
+ if (curr >= 0) {
size = chain_block_size(curr);
- next = chain_block_next(curr);
-
- if (size == req) {
- del_chain_block(prev, req, next);
+ if (likely(size > req)) {
+ del_chain_block(0, size, chain_block_next(curr));
+ add_chain_block(curr + req, size - req);
return curr;
}
-
- if (size > max_size) {
- max_prev = prev;
- max_curr = curr;
- max_next = next;
- max_size = size;
- }
- }
-
- if (likely(max_size > req)) {
- del_chain_block(max_prev, max_size, max_next);
- add_chain_block(max_curr + req, max_size - req);
- return max_curr;
}
/*
@@ -2843,8 +2837,7 @@ static int alloc_chain_hlocks(int req)
if (curr < 0)
continue;
- del_chain_block(bucket - MAX_CHAIN_BUCKETS, size,
- chain_block_next(curr));
+ del_chain_block(bucket, size, chain_block_next(curr));
add_chain_block(curr + req, size - req);
return curr;
}
next prev parent reply other threads:[~2020-02-04 13:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 16:41 [PATCH v5 0/7] locking/lockdep: Reuse zapped chain_hlocks entries Waiman Long
2020-02-03 16:41 ` [PATCH v5 1/7] locking/lockdep: Decrement irq context counters when removing lock chain Waiman Long
2020-02-03 16:41 ` [PATCH v5 2/7] locking/lockdep: Display irq_context names in /proc/lockdep_chains Waiman Long
2020-02-03 16:41 ` [PATCH v5 3/7] locking/lockdep: Track number of zapped classes Waiman Long
2020-02-03 16:41 ` [PATCH v5 4/7] locking/lockdep: Throw away all lock chains with zapped class Waiman Long
2020-02-03 16:41 ` [PATCH v5 5/7] locking/lockdep: Track number of zapped lock chains Waiman Long
2020-02-03 16:41 ` [PATCH v5 6/7] locking/lockdep: Reuse freed chain_hlocks entries Waiman Long
2020-02-04 12:36 ` Peter Zijlstra
2020-02-04 14:54 ` Waiman Long
2020-02-04 16:45 ` Waiman Long
2020-02-05 9:41 ` Peter Zijlstra
2020-02-05 13:59 ` Waiman Long
2020-02-04 15:42 ` Peter Zijlstra
2020-02-04 16:12 ` Waiman Long
2020-02-04 16:26 ` Waiman Long
2020-02-04 16:57 ` Waiman Long
2020-02-05 9:48 ` Peter Zijlstra
2020-02-05 14:03 ` Waiman Long
2020-02-03 16:41 ` [PATCH v5 7/7] locking/lockdep: Add a fast path for chain_hlocks allocation Waiman Long
2020-02-04 12:47 ` Peter Zijlstra
2020-02-04 15:07 ` Waiman Long
2020-02-04 13:18 ` Peter Zijlstra
2020-02-04 13:44 ` Peter Zijlstra [this message]
2020-02-04 18:02 ` 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=20200204134446.GQ14946@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;
as well as URLs for NNTP newsgroup(s).