linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
	Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	RT <linux-rt-users@vger.kernel.org>
Subject: Re: [rfc patch] drivers/block/zram: Replace bit spinlocks with rtmutex for -rt
Date: Mon, 4 Apr 2016 09:27:57 +0900	[thread overview]
Message-ID: <20160404002756.GA6164@swordfish> (raw)
In-Reply-To: <20160401104221.GB29603@linutronix.de>

On (04/01/16 12:42), Sebastian Andrzej Siewior wrote:
> >They're nondeterministic, and lead to ___might_sleep() splats in -rt.
> >OTOH, they're a lot less wasteful than an rtmutex per page.
> Applied.
> Although I'm disapointed about Sergey's argument against the spinlock in
> general due to a few bytes used by lockdep which can be disabled. Not to
> mention the usefull debug facility lockdep provides if one decides to
> use.

I'll take a look.

	-ss

      reply	other threads:[~2016-04-04  0:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 10:19 [rfc patch] drivers/block/zram: Replace bit spinlocks with rtmutex for -rt Mike Galbraith
2016-03-22 10:34 ` Mike Galbraith
2016-03-30  8:56 ` Sebastian Andrzej Siewior
2016-03-30  9:13   ` Sergey Senozhatsky
2016-03-30  9:19     ` Sebastian Andrzej Siewior
2016-03-30  9:23   ` Mike Galbraith
2016-03-31  2:08     ` Mike Galbraith
2016-04-01 10:42       ` Sebastian Andrzej Siewior
2016-04-04  0:27         ` Sergey Senozhatsky [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=20160404002756.GA6164@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=umgwanakikbuti@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;
as well as URLs for NNTP newsgroup(s).