From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Re: Memory allocation and the "prealloc" procfile Date: Fri, 08 Apr 2005 13:06:43 +0200 Message-ID: References: <1112789019.6835.30.camel@andys_dellm60.ss82amr.net> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Clemens Ladisch Cc: Andy Robinson , ALSA devel List-Id: alsa-devel@alsa-project.org 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