From: Mike Galbraith <efault@gmx.de>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, rsc@pengutronix.de
Subject: Re: Issues with Patch: "sched: Improve latencies and throughput"
Date: Thu, 01 Apr 2010 21:35:50 +0200 [thread overview]
Message-ID: <1270150550.6413.27.camel@marge.simson.net> (raw)
In-Reply-To: <20100401084311.GL10342@pengutronix.de>
On Thu, 2010-04-01 at 10:43 +0200, Michael Grzeschik wrote:
> On Thu, Apr 01, 2010 at 07:49:46AM +0200, Mike Galbraith wrote:
> > On Thu, 2010-04-01 at 00:31 +0200, Michael Grzeschik wrote:
> > > We are using an arm mx31 embedded cpu with the v2.6.34 Kernelrelease and
> > > realized some issues with the scheduling behaviour the patch "sched:
> > > Improve latencies and throughput" [1] by Mike Galbraith introduced to
> > > the kernel.
> > >
> > > When we used the alsa utility aplay to pipe some audio through an
> > > usbaudio device and put some scheduling overhead on the device, the
> > > amount of underruns, due to the not fast enough refilled ring buffer,
> > > was noticable increased with that patch [1] applied. Until we reverse
> > > applied the patch the amount of underruns was appreciable lower.
> >
> > Testcase?
>
> What we did was:
>
> # Copy some audiofile to /dev/shm
> $ cp audiofile.wav /dev/shm
>
> # Play that file with aplay in background
> $ aplay /dev/shm/auduifile.wav &
>
> # Put some scheduling load on the system
> $ hackbench 6
>
> We did use this on an MX31 from Freescale running with about 500 MHz and
> the generic usbaudio driver to play the audio throgh an C-Media USB
> audiodongle.
Hm. I don't _think_ you've demonstrated a clear problem yet.
Q: how much CPU is aplay routinely using on this platform?
-Mike
prev parent reply other threads:[~2010-04-01 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 22:31 Michael Grzeschik
2010-04-01 5:49 ` Mike Galbraith
2010-04-01 8:43 ` Michael Grzeschik
2010-04-01 19:35 ` Mike Galbraith [this message]
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=1270150550.6413.27.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgr@pengutronix.de \
--cc=rsc@pengutronix.de \
/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
Powered by JetHome