On Tue, Nov 15, 2016 at 02:29:16PM -0600, Christoph Lameter wrote: > > > > There is a deadlock, Peter!!! > > > > Describe please? Also, have you tried disabling RT_RUNTIME_SHARE ? > > > > > The description was given earlier in the the thread and the drawbacks of > using RT_RUNTIME_SHARE as well.
I've not seen a deadlock described. It either was an unbounded priority inversion or a starvation issue, both of which are 'design' features of the !rt kernel. Neither things are new, so its not a regression either. And, as stated, I'm not really happy to muck with this known troublesome code and add features for which we must then maintain feature parity when replacing it either. On top of which, the implementation had issues; now I know you're the blinder kind of person that disregards everything not in his immediate interest, but if you'd looked at the patch you'd have seen he'd added code the idle entry path, which will slow down every single to-idle transition.
