linux-kernel - Re: [alsa-devel] change kmalloc into vmalloc for large memory allocations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 4 Mar 2014 11:46:41 +0800
From:	Mark Brown <broonie@...nel.org>
To:	"Wang, Yalin" <Yalin.Wang@...ymobile.com>
Cc:	'Takashi Iwai' <tiwai@...e.de>,
	'Lars-Peter Clausen' <lars@...afoo.de>,
	"'alsa-devel@...a-project.org'" <alsa-devel@...a-project.org>,
	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
	Liam Girdwood <liam.r.girdwood@...el.com>
Subject: Re: [alsa-devel] change kmalloc into vmalloc for large memory
 allocations

On Mon, Mar 03, 2014 at 11:33:24PM +0800, Wang, Yalin wrote:
> Hi Takashi,
> 
> I see,
> 
> I just want to save low memory for kmalloc use,
> So I want to filter out large memory allocations
> To use vmalloc instead ,
> 
> It will be preferable, if there is a better solution :)
> 
> Thank you for your clarification.

Don't top post.  

Without having seen the earlier mails in the thread I'm not 100% sure on
the specifics here but wouldn't a more generic solution be to deal with
this in the memory management code?  

As far as I can tell the concern is that the runtime structures are
taking up too much memory when allocated using kzallloc?  We're also
doing lots of small allocations for things like DAPM which will
presumably also be burning this memory and will I expect for most
systems end up being more than that consumed by the runtime structures.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)