All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Andy Robinson <andy@seventhstring.com>,
	ALSA devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: Memory allocation and the "prealloc" procfile
Date: Fri, 08 Apr 2005 13:06:43 +0200	[thread overview]
Message-ID: <s5h1x9lr0ho.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.HPX.4.33n.0504081252410.22473-100000@studcom.urz.uni-halle.de>

At Fri, 8 Apr 2005 12:55:29 +0200 (METDST),
Clemens Ladisch wrote:
> 
> Andy Robinson wrote:
> > But I'm still curious to know, what is all that
> > /proc/asound/card0/pcm0p/sub0/prealloc memory used for?
> 
> For the buffer. :)
> 
> > I specify 128k but only get a 32k buffer reported by
> > SNDCTL_DSP_GETOSPACE (and one of my users gets only 4k of buffer)
> 
> Doesn't happen on my machine.  What parameters are you using?

I guess this depends on the order of ioctls.

Each ioctl limits the available configuration.  At each time either
fragment size,  fragment, format, channels, etc. is changed via ioctl,
the max. buffer size is recalculated, but it won't grow once if the
size is limited via the constraint.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      reply	other threads:[~2005-04-08 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050405192033.6B8A88993B@sc8-sf-spam1.sourceforge.net>
2005-04-06 12:03 ` Memory allocation and the "prealloc" procfile Andy Robinson
2005-04-08 10:55   ` Clemens Ladisch
2005-04-08 11:06     ` Takashi Iwai [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=s5h1x9lr0ho.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=andy@seventhstring.com \
    --cc=clemens@ladisch.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.