From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: RT, what to do about up/down_read_non_owner()
Date: Mon, 06 Jun 2016 11:07:08 +0200 [thread overview]
Message-ID: <1465204028.11062.3.camel@gmail.com> (raw)
In-Reply-To: <c3b6168e-dde1-fb3b-36e6-5ff4c75e7355@linutronix.de>
On Mon, 2016-06-06 at 09:49 +0200, Sebastian Andrzej Siewior wrote:
> On 06/05/2016 08:57 AM, Mike Galbraith wrote:
> > Greetings,
> >
> > In v4.7, Al added those buggers to NFS. BCACHE is disabled in RT
> > because of same.. but that's a somewhat suboptimal solution for
> > something as widely used as NFS.
> >
> > Suggestions? I reverted the offending commit to get 4.7-rt up and
> > running, but that's not gonna fly long term.
>
> This API should be avoided according to the comment and completions
> should be used. I am for removal of those. Were the locking people okay
> with this change in the first place or did this just sneak in?
It just snuck in. Al reworked sillyunlink, whacking the wait_event()
stuff that was there, using annoying $subject instead.
-Mike
next prev parent reply other threads:[~2016-06-06 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 6:57 RT, what to do about up/down_read_non_owner() Mike Galbraith
2016-06-06 7:49 ` Sebastian Andrzej Siewior
2016-06-06 9:07 ` Mike Galbraith [this message]
2016-06-06 9:50 ` Mike Galbraith
2016-06-06 19:24 ` Al Viro
2016-06-07 2:39 ` Mike Galbraith
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=1465204028.11062.3.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.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 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.