From: Byungchul Park <byungchul.park@lge.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, npiggin@suse.de,
gregkh@linuxfoundation.org, minchan@kernel.org,
sergey.senozhatsky.work@gmail.com
Subject: Re: [PATCH 3/5] lockdep: Apply bit_spin_lock lockdep to zram
Date: Tue, 21 Jun 2016 10:05:08 +0900 [thread overview]
Message-ID: <20160621010508.GJ2279@X58A-UD3R> (raw)
In-Reply-To: <20160620153619.GA649@swordfish>
On Tue, Jun 21, 2016 at 12:36:19AM +0900, Sergey Senozhatsky wrote:
>
> Hello,
>
> just for information
Thank you for informing it.
>
> there was a proposal from -rt people to use normal spinlocks
> for table's entries, rather that bitspinlock. I had a patch
> some time ago, will obtain some performance data and post
> RFC [may be tomorrow].
>
> -ss
>
next prev parent reply other threads:[~2016-06-21 1:06 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
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 [this message]
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=20160621010508.GJ2279@X58A-UD3R \
--to=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=peterz@infradead.org \
--cc=sergey.senozhatsky.work@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox