Thread (6 messages) 6 messages, 3 authors, 2016-06-07

Re: RT, what to do about up/down_read_non_owner()

From: Mike Galbraith <hidden>
Date: 2016-06-06 09:50:08

(CCs Al, who knows, maybe he'll make them go *poof*)

On Mon, 2016-06-06 at 11:07 +0200, Mike Galbraith wrote:
On Mon, 2016-06-06 at 09:49 +0200, Sebastian Andrzej Siewior wrote:
quoted
On 06/05/2016 08:57 AM, Mike Galbraith wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help