From: Peter Zijlstra <peterz@infradead.org>
To: Byungchul Park <byungchul.park@lge.com>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, npiggin@suse.de,
sergey.senozhatsky@gmail.com, gregkh@linuxfoundation.org,
minchan@kernel.org
Subject: Re: [PATCH 1/5] lockdep: Implement bitlock map allocator
Date: Thu, 30 Jun 2016 14:59:19 +0200 [thread overview]
Message-ID: <20160630125919.GD30154@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1466398515-1005-2-git-send-email-byungchul.park@lge.com>
On Mon, Jun 20, 2016 at 01:55:11PM +0900, Byungchul Park wrote:
> +struct bitlock_map {
> + struct hlist_node hash_entry;
> + unsigned long bitaddr; /* ID */
> + struct lockdep_map map;
> + int ref; /* reference count */
> +};
So this is effectively bigger than just adding a struct lockdep_map into
whatever structure holds the bit spinlock to begin with.
What is the gain?
> +static inline unsigned long get_bitaddr(int bitnum, unsigned long *addr)
> +{
> + return (unsigned long)((char *)addr + bitnum);
> +}
And given you keep these lockdep_map thingies out-of-line, the original
structure remains dense and thus the above munging can easily result in
collisions.
Now, I suppose its rather unlikely, but given its entirely silent if it
happens, this is bad.
next prev parent reply other threads:[~2016-06-30 12:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 4:55 [PATCH 0/5] Implement bitlock map allocator Byungchul Park
2016-06-20 4:55 ` [PATCH 1/5] lockdep: " Byungchul Park
2016-06-30 12:59 ` Peter Zijlstra [this message]
2016-07-01 0:24 ` Byungchul Park
2016-07-01 7:53 ` Peter Zijlstra
2016-07-04 7:29 ` Byungchul Park
2016-07-07 10:22 ` Byungchul Park
2016-07-13 20:17 ` Peter Zijlstra
2016-07-18 1:46 ` Byungchul Park
2016-06-20 4:55 ` [PATCH 2/5] lockdep: Apply bitlock to bit_spin_lock Byungchul Park
2016-06-20 4:55 ` [PATCH 3/5] lockdep: Apply bit_spin_lock lockdep to zram Byungchul Park
2016-06-20 15:36 ` Sergey Senozhatsky
2016-06-21 1:05 ` Byungchul Park
2016-06-20 4:55 ` [PATCH 4/5] fs/buffer.c: Remove trailing white space Byungchul Park
2016-06-20 4:55 ` [PATCH 5/5] lockdep: Apply bit_spin_lock lockdep to BH_Uptodate_Lock Byungchul Park
2016-06-29 12:45 ` [PATCH 0/5] Implement bitlock map allocator Byungchul Park
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=20160630125919.GD30154@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=byungchul.park@lge.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=npiggin@suse.de \
--cc=sergey.senozhatsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.