All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Heineken <Lars.Heineken@gmx.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Opening dev/dsp takes very long
Date: Fri, 19 Mar 2004 22:58:21 +0100	[thread overview]
Message-ID: <405B6CFD.9070303@gmx.de> (raw)
In-Reply-To: <405AE7B8.6080603@gmx.de>

I used the latest alsa-tarballs to upgrade alsa-lib, alsa-driver and 
alsa-oss.
To make it short: The problem is even worse now !

This is the output from strace (relevant part):

      .
      .
      0.000531 ioctl(4, SNDCTL_DSP_RESET, 0) = 0
      0.000232 ioctl(4, SNDCTL_DSP_GETFMTS, 0xbffff668) = 0
      0.510506 ioctl(4, SNDCTL_DSP_SETFMT, 0xbffff668) = 0
      0.506515 ioctl(4, SNDCTL_DSP_STEREO, 0xbffff668) = 0
      0.504940 ioctl(4, SOUND_PCM_READ_RATE, 0xbffff668) = 0
      0.065604 ioctl(4, SNDCTL_DSP_GETBLKSIZE, 0x80a5824) = 0
      0.000302 ioctl(4, SNDCTL_DSP_SYNC, 0) = 0
      0.000250 munmap(0x40016000, 4096)  = 0
      .
      .


..now it's not just a single call that takes too long, but _three_ of them.

There has to be someone who nows about the changes made from the alsa 
used in 2.6.4 and the current release, this way we could probably locate 
the source for the _additional_ delay introduced, maybe that'll lead us 
to a solution for the whole issue ?





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-19 21:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13 20:01 Opening dev/dsp takes very long Lars Heineken
2004-03-13 20:24 ` Additional info: " Lars Heineken
2004-03-15 10:35 ` Takashi Iwai
2004-03-15 20:22   ` Lars Heineken
2004-03-16  8:19     ` Clemens Ladisch
2004-03-16  8:49       ` Lars Heineken
2004-03-16 19:04         ` Lars Heineken
2004-03-19 12:29         ` Lars Heineken
2004-03-19 21:58           ` Lars Heineken [this message]
2004-03-19 23:56             ` James Courtier-Dutton
2004-03-20  8:20               ` Lars Heineken
2004-03-20 13:24                 ` Jaroslav Kysela
2004-03-20 16:09                   ` Lars Heineken
2004-03-20 16:11                     ` Jaroslav Kysela
2004-03-20 16:59                       ` Lars Heineken
2004-03-20 17:13                   ` Tommi Sakari Uimonen
2004-03-20 17:12                     ` Jaroslav Kysela

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=405B6CFD.9070303@gmx.de \
    --to=lars.heineken@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.