From: Peter Williams <pwil3058@bigpond.net.au>
To: Mike Galbraith <efault@gmx.de>
Cc: Con Kolivas <kernel@kolivas.org>,
Rene Herman <rene.herman@keyaccess.nl>,
Lee Revell <rlrevell@joe-job.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.17-rc2+ regression -- audio skipping
Date: Mon, 22 May 2006 16:34:07 +1000 [thread overview]
Message-ID: <44715B5F.6060205@bigpond.net.au> (raw)
In-Reply-To: <1148277658.10520.9.camel@homer>
Mike Galbraith wrote:
> On Mon, 2006-05-22 at 15:38 +1000, Peter Williams wrote:
>
>> In my schedulers I generalize background to "soft cpu rate caps" with a
>> cap of zero being the same as background. I have patches to add both
>> soft and hard cpu rate caps to the standard scheduler but I'm sitting on
>> them until things settle down a bit.
>
> I look forward to seeing them. Any chance of a preview?
>
I'll post them as a "request for comment" tomorrow. I'm still undecided
about the best user space interface for using them. At the moment, I
have mechanisms to set them via /proc which is very handy for testing
but not necessarily the best interface for general use. Other options
are via rlimits or a syscall.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-05-22 6:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 20:24 2.6.17-rc2+ regression -- audio skipping Rene Herman
2006-05-21 21:30 ` Lee Revell
2006-05-22 0:10 ` Rene Herman
2006-05-22 0:17 ` Rene Herman
2006-05-22 0:33 ` Con Kolivas
2006-05-22 2:14 ` Mike Galbraith
2006-05-22 2:43 ` Con Kolivas
2006-05-22 3:10 ` Mike Galbraith
2006-05-22 3:30 ` Peter Williams
2006-05-22 4:53 ` Mike Galbraith
2006-05-22 5:38 ` Peter Williams
2006-05-22 6:00 ` Mike Galbraith
2006-05-22 6:34 ` Peter Williams [this message]
2006-05-23 5:22 ` Peter Williams
2006-05-22 3:26 ` Peter Williams
2006-05-22 18:22 ` Rene Herman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44715B5F.6060205@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rene.herman@keyaccess.nl \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.