From: "Parag Warudkar" <parag.warudkar@gmail.com>
To: "Peter Zijlstra" <a.p.zijlstra@chello.nl>
Cc: "Ingo Molnar" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
"Frans Pop" <elendil@planet.nl>, "Mike Galbraith" <efault@gmx.de>
Subject: Re: Horrendous Audio Stutter - current git
Date: Fri, 2 May 2008 07:10:37 -0400 [thread overview]
Message-ID: <82e4877d0805020410u78c6f03fr8e8e53d5a19f6846@mail.gmail.com> (raw)
In-Reply-To: <1209717278.13978.136.camel@twins>
On Fri, May 2, 2008 at 4:34 AM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Thu, 2008-05-01 at 20:14 -0400, Parag Warudkar wrote:
>
> Parag, would you also test with !NEW_FAIR_SLEEPERS to see if that solves
> your problem?
>
> The easiest way to disable it is (assumes you have debugfs mounted
> at /debug):
>
> # echo NO_NEW_FAIR_SLEEPERS > /debug/sched_features
Seems to make it stutter a little less - but still not usable.
>
> You can also disable NORMALIZED_SLEEPER that way (of course you would
> first have to enable NEW_FAIR_SLEEPERS again):
>
> # echo NO_NORMALIZED_SLEEPER > /debug/sched_features
>
No significant difference from NO_NEW_FAIR_SLEEPERS that I can tell.
> So by default we have both enabled; could you report if either
>
> NO_NEW_FAIR_SLEEPERS
>
> NEW_FAIR_SLEEPERS + NO_NORMALIZED_SLEEPERS
>
> works for you?
I would say no - the audio still is unusable - slightly better with
NO_NEW_FAIR_SLEEPERS, no difference with the other.
But per Mike's suggestion if I disable CONFIG_GROUP_SCHED ,
CONFIG_FAIR_GROUP_SCHED and CONFIG_USER_SCHED, even with
NEW_FAIR_SLEEPERS audio is good again, which does not change with
NO_NEW_FAIR_SLEEPERS. (No skips for long time under -j8 - still skips
a _very_ tiny bit - noticeable if I listen too carefully - but we can
ignore that for the time being.)
Mike - the GROUP_SCHED stuff is set to y in the Ubuntu kernel and I
have no audio skips - may be a regression introduced after 2.6.24?
But why is the GROUP_SCHED stuff default y if it so unusable?
>
> Also, could you apply this patch, and report the bonus_max value for
> your music player under all three scenarios?
>
I see Frans already reported that and there was some conclusion - let
me know if more data will help.
Thanks!
Parag
next prev parent reply other threads:[~2008-05-02 11:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 0:14 Parag Warudkar
2008-05-02 8:34 ` Peter Zijlstra
2008-05-02 10:32 ` Frans Pop
2008-05-02 10:35 ` Peter Zijlstra
2008-05-02 11:08 ` Peter Zijlstra
2008-05-02 11:37 ` Frans Pop
2008-05-02 11:39 ` Peter Zijlstra
2008-05-02 11:45 ` Frans Pop
2008-05-02 11:51 ` Peter Zijlstra
2008-05-02 12:06 ` Frans Pop
2008-05-02 12:22 ` Parag Warudkar
2008-05-02 13:21 ` Dhaval Giani
2008-05-02 11:10 ` Parag Warudkar [this message]
2008-05-02 12:09 ` Mike Galbraith
2008-05-02 12:21 ` Parag Warudkar
2008-05-02 12:37 ` Mike Galbraith
2008-05-02 15:02 ` Mike Galbraith
2008-05-02 15:49 ` Frans Pop
2008-05-02 18:53 ` Frans Pop
2008-05-02 19:27 ` Mike Galbraith
2008-05-02 19:56 ` 'global' rq->clock (was Re: Horrendous Audio Stutter - current git) Peter Zijlstra
2008-05-02 20:38 ` Guillaume Chazarain
2008-05-02 20:46 ` Peter Zijlstra
2008-05-02 22:00 ` 'global' rq->clock David Miller
2008-05-02 21:48 ` David Miller
2008-05-02 10:09 ` Arjan van de Ven
2008-05-04 12:12 ` Peter Zijlstra
2008-05-02 22:07 ` Peter Zijlstra
2008-05-03 8:28 ` Ingo Molnar
2008-05-03 9:05 ` David Miller
2008-05-03 10:10 ` Ingo Molnar
2008-05-03 19:27 ` David Miller
2008-05-03 19:37 ` Ingo Molnar
2008-05-03 22:30 ` Benjamin Herrenschmidt
2008-05-03 22:38 ` Ingo Molnar
2008-05-03 23:04 ` David Miller
2008-05-03 23:36 ` David Miller
2008-05-03 23:38 ` Ingo Molnar
2008-05-03 23:40 ` David Miller
2008-05-03 23:47 ` Ingo Molnar
2008-05-04 2:22 ` Benjamin Herrenschmidt
2008-05-03 19:28 ` David Miller
2008-05-03 19:39 ` Ingo Molnar
2008-05-03 6:20 ` 'global' rq->clock (was Re: Horrendous Audio Stutter - current git) Mike Galbraith
2008-05-02 19:38 ` Horrendous Audio Stutter - current git Mike Galbraith
2008-05-03 7:13 ` Frans Pop
2008-05-03 7:39 ` Mike Galbraith
2008-05-07 8:26 ` Frans Pop
2008-05-07 8:32 ` Ingo Molnar
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=82e4877d0805020410u78c6f03fr8e8e53d5a19f6846@mail.gmail.com \
--to=parag.warudkar@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®