From: Takashi Iwai <tiwai@suse.de>
To: Andy Robinson <andy@seventhstring.com>
Cc: ALSA devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Memory allocation and the "prealloc" procfile
Date: Tue, 05 Apr 2005 19:16:39 +0200 [thread overview]
Message-ID: <s5hwtrhf8js.wl@alsa2.suse.de> (raw)
In-Reply-To: <1112605417.6910.26.camel@andys_dellm60.ss82amr.net>
At Mon, 04 Apr 2005 10:03:37 +0100,
Andy Robinson wrote:
>
> I'm using Mandrake 10.1 on a DELL Precision M60.
> Soundcard is Intel 82801DB-ICH4
> ALSA version 1.0.6
>
> By default, /proc/asound/card0/pcm0p/sub0/prealloc contains the number
> 64 and SNDCTL_DSP_GETOSPACE reports a total of 16k bytes output space
> available. If I
> echo 128 >/proc/asound/card0/pcm0p/sub0/prealloc
> then SNDCTL_DSP_GETOSPACE reports a total of 32k bytes.
>
> My question is, what is the rest of the "prealloc" memory being used
> for? And how can I change the amounts used for whatever other purposes,
> so as to get a bigger SNDCTL_DSP_GETOSPACE buffer? It's not such a
> problem for me but one of my users reports that with a 128k "prealloc",
> he still gets only 4k from SNDCTL_DSP_GETOSPACE. Is it perhaps an ALSA
> version issue?
It might be. It's worth to try the latest ALSA version, anyway.
If you want a bigger buffer, you can call SNDCTL_DSP_SETFRAGMENT ioctl
to specify the fragments and its size explicitly.
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
next prev parent reply other threads:[~2005-04-05 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 9:03 Memory allocation and the "prealloc" procfile Andy Robinson
2005-04-05 17:16 ` Takashi Iwai [this message]
[not found] <20050405192033.6B8A88993B@sc8-sf-spam1.sourceforge.net>
2005-04-06 12:03 ` Andy Robinson
[not found] <20050408154303.E61098C466@sc8-sf-spam1.sourceforge.net>
2005-04-08 16:07 ` Andy Robinson
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=s5hwtrhf8js.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=andy@seventhstring.com \
/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.