From: Michael Grzeschik <mgr@pengutronix.de>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org, rsc@pengutronix.de
Subject: Re: Issues with Patch: "sched: Improve latencies and throughput"
Date: Thu, 1 Apr 2010 10:43:11 +0200 [thread overview]
Message-ID: <20100401084311.GL10342@pengutronix.de> (raw)
In-Reply-To: <1270100986.6707.156.camel@marge.simson.net>
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.
Expected results with that patch:
underrun!!! (at least 323.946 ms long) < -- aplay
underrun!!! (at least 59.477 ms long) < -- "
underrun!!! (at least 194.873 ms long) < -- "
Time: 7.048 < -- hackbench
Time: 6.841 < -- "
underrun!!! (at least 115.456 ms long) < -- aplay
underrun!!! (at least 37.849 ms long) < -- "
underrun!!! (at least 588.637 ms long) < -- "
Time: 7.23 < -- hackbench
results without the patch:
Time: 3.728 < -- hackbench
underrun!!! (at least 58.557 ms long) < -- aplay
Time: 3.771 < -- hackbench
underrun!!! (at least 97.538 ms long) < -- aplay
Time: 3.732 < -- hackbench
Time: 3.630 < -- ....
Time: 3.636
Time: 3.643
Thanks,
mgr
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2010-04-01 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 22:31 Issues with Patch: "sched: Improve latencies and throughput" Michael Grzeschik
2010-04-01 5:49 ` Mike Galbraith
2010-04-01 8:43 ` Michael Grzeschik [this message]
2010-04-01 19:35 ` Mike Galbraith
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=20100401084311.GL10342@pengutronix.de \
--to=mgr@pengutronix.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).