Messages in this thread | | | From | Nick Piggin <> | Subject | Re: [PATCH 6/6] sched: disabled rt-bandwidth by default | Date | Tue, 26 Aug 2008 19:54:47 +1000 |
| |
On Tuesday 26 August 2008 19:30, Ingo Molnar wrote: > * Nick Piggin <nickpiggin@yahoo.com.au> wrote: > > So... no reply to this? I'm really wondering how it's OK to break > > documented standards and previous Linux behaviour by default for > > something that it is trivial to solve in userspace? [...] > > I disagree
Your arguments were along the line of:
* It probably doesn't break anything (except we had somebody report that it breaks their app)
* If it does break something then they must be doing something stupid (I refuted that because there are several legitimate ways to use rt scheduling that is broken by this)
* We have many other APIs and tools that don't conform to posix (why is that a reason to break this one?)
* We should break the API to cater for stupid users and distros who create local DoS and/or lock up their boxes (except this is trivial to solve by setting sysctls or having a watchdog or using sysrq)
So did I miss some really good argument, or do you really think the above arguments are a good reason to break the API? If the latter, then we have to just agree to disagree and I'll ask Linus to arbitrate. OK?
| |