From: Ben Hutchings <ben@decadent.org.uk>
To: Kent Overstreet <kmo@daterainc.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: PREEMPT_RT vs bcache
Date: Wed, 07 Aug 2013 23:08:42 +0200 [thread overview]
Message-ID: <1375909722.27403.39.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20130807205357.GD11612@kmo-pixel>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On Wed, 2013-08-07 at 13:53 -0700, Kent Overstreet wrote:
> On Wed, Aug 07, 2013 at 10:28:18PM +0200, Ben Hutchings wrote:
> > As Kent said back in 2011 (commit 84759c6d18c5), bcache needs
> > {down,up}_read_non_owner(). But these are not implemented by the -rt
> > patchset when PREEMPT_RT_FULL is enabled. Can they be added, or is
> > there a fundamental conflict here?
>
> You should be able to cherry pick
> 84759c6d18c5144432781ddca037d929ee9db8a5 (Revert "rw_semaphore: remove
> up/down_read_non_owner") - that went in when bcache was merged.
That's the commit I was referring to. But the -rt patchset has a
separate implementation of semaphores for PREEMPT_RT_FULL.
Ben.
--
Ben Hutchings
Experience is what causes a person to make new mistakes instead of old ones.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-07 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 20:28 Ben Hutchings
2013-08-07 20:53 ` Kent Overstreet
2013-08-07 21:08 ` Ben Hutchings [this message]
2013-08-07 21:09 ` Kent Overstreet
2013-08-07 21:12 ` Uwe Kleine-König
2013-08-08 7:26 ` Christoph Hellwig
2013-08-08 7:43 ` Kent Overstreet
2013-08-08 12:11 ` Christoph Hellwig
2013-09-12 15:01 ` Thomas Gleixner
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=1375909722.27403.39.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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®