All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: root@chaos.analogic.com, Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@suse.cz>, Russ Garrett <rg@tcslon.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Audio skipping with alsa
Date: Thu, 11 Sep 2003 01:28:35 +1000	[thread overview]
Message-ID: <200309110128.35543.kernel@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0309101037120.12986@chaos>

On Thu, 11 Sep 2003 00:45, Richard B. Johnson wrote:
> I don't see the driver in linux-2.4.22/drivers/sound, so I can't
> look at it directly, but normally all you have to do is keep
> a FIFO full (not empty) during play. There should not be any
> scheduling issues with sound chips although I am seeing too
> much of that lately. Maybe  somebody should look at the driver
> before the scheduler is blamed. Perhaps the driver is not
> designed properly so it assumes the user-mode code can do
> something it can't possibly be expected to do with any
> reliability. For instance, perhaps it's the user-mode's
> responsibility to keep a FIFO full? And, you can never
> guarantee that.

That may be the case, but there is a very clear problem with the vanilla 
scheduler that can cause too low priority for audio apps for up to 25 seconds 
after starting a new thread (eg new song). In turn they will skip madly when 
any higher priority task uses a burst of cpu and repeatedly preempts it (X, 
mozilla, the neighbour's dog...). Only the largest buffer audio cards wont 
skip with the vanilla scheduler, and _no_ amount of single cpu capability 
today is enough to avoid the scheduler based starvation. So while it never 
hurts to keep an eye on driver performance, the scheduler itself _must_ be 
fixed to prevent this happening.

Con


  reply	other threads:[~2003-09-10 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 14:14 Audio skipping with alsa Russ Garrett
2003-09-10 13:23 ` Takashi Iwai
2003-09-10 13:38   ` Jaroslav Kysela
2003-09-10 13:45     ` Takashi Iwai
2003-09-10 14:45       ` Richard B. Johnson
2003-09-10 15:28         ` Con Kolivas [this message]
2003-09-10 15:43         ` Takashi Iwai
2003-09-10 17:47         ` Russ Garrett
2003-09-10 18:16           ` Chris Meadors
2003-09-10 18:27             ` Takashi Iwai

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=200309110128.35543.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=rg@tcslon.com \
    --cc=root@chaos.analogic.com \
    --cc=tiwai@suse.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 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.