From: Christoph Hellwig <hch@infradead.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Kent Overstreet <kmo@daterainc.com>,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
Subject: Re: PREEMPT_RT vs bcache
Date: Thu, 8 Aug 2013 00:26:23 -0700 [thread overview]
Message-ID: <20130808072623.GA3509@infradead.org> (raw)
In-Reply-To: <1375907298.27403.35.camel@deadeye.wl.decadent.org.uk>
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?
How did they get back in at all? I'm pretty sure I removed them for
good reason.
next prev parent reply other threads:[~2013-08-08 7:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 20:28 PREEMPT_RT vs bcache Ben Hutchings
2013-08-07 20:53 ` Kent Overstreet
2013-08-07 21:08 ` Ben Hutchings
2013-08-07 21:09 ` Kent Overstreet
2013-08-07 21:12 ` Uwe Kleine-König
2013-08-08 7:26 ` Christoph Hellwig [this message]
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=20130808072623.GA3509@infradead.org \
--to=hch@infradead.org \
--cc=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