From: Mark Brown <broonie@kernel.org>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: 'Takashi Iwai' <tiwai@suse.de>,
'Lars-Peter Clausen' <lars@metafoo.de>,
"'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
Liam Girdwood <liam.r.girdwood@intel.com>
Subject: Re: [alsa-devel] change kmalloc into vmalloc for large memory allocations
Date: Tue, 4 Mar 2014 11:46:41 +0800 [thread overview]
Message-ID: <20140304034641.GY2411@sirena.org.uk> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D102844605F396@CNBJMBX05.corpusers.net>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-03-04 3:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 8:15 [alsa-devel] change kmalloc into vmalloc for large memory allocations Wang, Yalin
2014-02-28 8:54 ` Huang Shijie
2014-02-28 9:20 ` Wang, Yalin
2014-02-28 16:33 ` 'gregkh@linuxfoundation.org'
2014-03-03 2:51 ` Wang, Yalin
2014-03-03 3:08 ` 'gregkh@linuxfoundation.org'
2014-03-03 8:00 ` Wang, Yalin
2014-03-03 14:10 ` 'gregkh@linuxfoundation.org'
2014-03-04 7:30 ` [PATCH] netfilter:Change nf_conntrack modules to use vmalloc Wang, Yalin
2014-02-28 14:11 ` change kmalloc into vmalloc for large memory allocations Steven Rostedt
2014-02-28 14:19 ` Takashi Iwai
2014-03-03 1:55 ` Wang, Yalin
2014-03-03 9:19 ` Takashi Iwai
2014-03-03 9:23 ` Takashi Iwai
2014-03-03 11:13 ` Wang, Yalin
2014-03-03 11:34 ` [alsa-devel] " Lars-Peter Clausen
2014-03-03 11:36 ` Wang, Yalin
2014-03-03 11:45 ` Lars-Peter Clausen
2014-03-03 13:29 ` [alsa-devel] " Wang, Yalin
2014-03-03 14:22 ` Lars-Peter Clausen
2014-03-03 14:29 ` Wang, Yalin
2014-03-03 14:43 ` Takashi Iwai
2014-03-03 15:33 ` Wang, Yalin
2014-03-04 3:46 ` Mark Brown [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=20140304034641.GY2411@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Yalin.Wang@sonymobile.com \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox