Re: [patch, 2.6.11-rc2] sched: RLIMIT_RT_CPU_RATIO feature
[Posted February 8, 2005 by corbet]
| From: |
| Ingo Molnar <mingo-AT-elte.hu> |
| To: |
| Jack O'Quin <joq-AT-io.com> |
| Subject: |
| Re: [patch, 2.6.11-rc2] sched: RLIMIT_RT_CPU_RATIO feature |
| Date: |
| Wed, 2 Feb 2005 21:29:53 +0100 |
| Cc: |
| Andrew Morton <akpm-AT-osdl.org>,
Nick Piggin <nickpiggin-AT-yahoo.com.au>,
linux <linux-kernel-AT-vger.kernel.org>, CK Kernel <ck-AT-vds.kolivas.org>,
Chris Wright <chrisw-AT-osdl.org>, Lee Revell <rlrevell-AT-joe-job.com>,
alexn-AT-dsv.su.se, Arjan van de Ven <arjanv-AT-redhat.com>,
Rui Nuno Capela <rncbc-AT-rncbc.org>, utz <utz-AT-s2y4n2c.de>,
Paul Davis <paul-AT-linuxaudiosystems.com> |
| Archive-link: |
| Article,
Thread
|
* Jack O'Quin <joq@io.com> wrote:
> I guess you're right, Lee. I hadn't thought of it that way. It just
> looks broken to me because we have no standing in any normal kernel
> requirements process. That's a shame, but it does seem less like a
> systemic issue.
you have just as much standing, and you certainly went to great lengths
(writing patches, testing stuff, etc.) to address this issue - it is
just an unfortunate situation that the issue here is _not_ clear-cut at
all. It is a longstanding habit on lkml to try to solve things as
cleanly and generally as possible, but there are occasional cases where
this is just not possible.
e.g. technically it was much harder to write all the latency-fix patches
(and infrastructure around it) that are now in 2.6.11-rc2, but it was
also a much clearer issue, with clean solutions; so there was no
conflict about whether to do it and you'll reap the benefits of that in
2.6.11.
so forgive us this stubborness, it's not directed against you in person
or against any group of users, it's always directed at the problem at
hand. I think we can do the LSM thing, and if this problem comes up in
the future again, then maybe by that time there will be a better
solution. (e.g. it's quite possible that something nice will come out of
the various virtualization projects, for this problem area.)
Ingo
(
Log in to post comments)