From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Con Kolivas <kernel@kolivas.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: xmms (audio) skipping in 2.5 (not 2.4)
Date: Wed, 12 Mar 2003 15:42:27 -0800 [thread overview]
Message-ID: <86480000.1047512547@flay> (raw)
In-Reply-To: <20030312225945.GA5958@zaurus.ucw.cz>
>> > the "desktop tuning" of making the max timeslice==min timeslice. Try an
>> > -mm kernel with the scheduler tunables patch and try playing with the
>> > max timeslice. Most have found that <=25 will usually stop these skips.
>> > The default max timeslice of 300ms is just too long for the desktop and
>> > interactivity estimator.
>>
>> Heh, cool. I have the same patch in my tree too, fixed it without rebooting
>> even ;-) Still a *tiny* bit of skipping, but infinitely better than it was.
>
> Fixed without rebooting? You binary-patched
> kernel or what?
> Pavel
Nope, the sched tunables patch from Robert (which is in -mjb and -mm,
so I was already running) exposes those parameters out to userspace
for sysctl to change ... I just ran sysctl once, and it was done ;-)
M.
next prev parent reply other threads:[~2003-03-12 23:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 5:25 xmms (audio) skipping in 2.5 (not 2.4) Martin J. Bligh
2003-03-04 5:36 ` Con Kolivas
2003-03-04 5:52 ` Martin J. Bligh
2003-03-04 7:28 ` Con Kolivas
2003-03-04 7:48 ` Martin J. Bligh
2003-03-04 8:15 ` Con Kolivas
2003-03-04 10:00 ` Andrew McGregor
2003-03-04 15:59 ` Martin J. Bligh
2003-03-12 22:59 ` Pavel Machek
2003-03-12 23:42 ` Martin J. Bligh [this message]
2003-03-04 9:48 ` Giuliano Pochini
2003-03-04 14:13 ` Anton Blanchard
2003-03-04 14:18 ` Maciej Soltysiak
2003-03-04 14:31 ` Sean Neakums
2003-03-04 16:17 ` Martin J. Bligh
2003-03-04 18:39 ` Aaron Lehmann
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=86480000.1047512547@flay \
--to=mbligh@aracnet.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).