Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1374137
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule |
| Date | 2016-04-08 12:40 +0200 |
| Message-ID | <rlBZv-2oe-1@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <riEqS-P8-21@gated-at.bofh.it> <rjeE2-1I4-15@gated-at.bofh.it> <rjkgq-5Ym-7@gated-at.bofh.it> <rlli2-6NG-19@gated-at.bofh.it> <rlntw-7U-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 04/07/2016 09:04 PM, Mike Galbraith wrote: >> just to be clear: The patch I attached did _not_ work for you. > > Sorry, I didn't test. Marathon stress test session convinced me that > the lock added by -rt absolutely had to die. Okay. And the patch did that. I removed the lock. >>> If that lock dies, we can unpin when entering lock slow path and pin >>> again post acquisition with no ABBA worries as well, and not only does >>> existing hotplug work heaping truckloads better, -rt can perhaps help >>> spot trouble as the rewrite proceeds. >>> >>> Current state is more broken than ever.. if that's possible. >> >> And the two patches you attached here did? > > I've killed way too many NOPREEMPT kernels to make any rash -rt claims. > What I can tell you is that my 64 core DL980 running 4.6-rc2-rt13 plus > the two posted patches survived for ~20 hours before I had to break it > off because I needed the box. > > These two haven't been through _as_ much pounding as the two targeted > bandaids I showed have, but have been through quite a bit. Other folks > beating the living crap outta their boxen too would not be a bad idea. I see. So what I don't like are all the exceptions you have: one for RCU and one kernfs. There might come more in the future. So what I aim is the removal of the lock. > > -Mike > Sebastian
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-04-07 18:50 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-04-07 21:10 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-04-08 12:40 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-04-08 14:20 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-04-08 08:40 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-04-08 15:50 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-04-08 16:00 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-04-08 16:20 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-04-08 17:00 +0200
Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-04-08 18:50 +0200
csiph-web