From: Huang Shijie <b32955@freescale.com>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: "'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>,
"'broonie@opensource.wolfsonmicro.com'"
<broonie@opensource.wolfsonmicro.com>,
"'tiwai@suse.de'" <tiwai@suse.de>,
"'fweisbec@gmail.com'" <fweisbec@gmail.com>,
"'perex@perex.cz'" <perex@perex.cz>,
"'dmitry.torokhov@gmail.com'" <dmitry.torokhov@gmail.com>,
"'mingo@redhat.com'" <mingo@redhat.com>,
"'linux-input@vger.kernel.org'" <linux-input@vger.kernel.org>,
"'rydberg@euromail.se'" <rydberg@euromail.se>,
"'lrg@ti.com'" <lrg@ti.com>,
"'pablo@netfilter.org'" <pablo@netfilter.org>,
"'coreteam@netfilter.org'" <coreteam@netfilter.org>,
"'linux-arm-msm@vger.kernel.org'" <linux-arm-msm@vger.kernel.org>,
"'rostedt@goodmis.org'" <rostedt@goodmis.org>,
"'netfilter@vger.kernel.org'" <netfilter@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
'gregkh@linuxfoundation.org
Subject: Re: change kmalloc into vmalloc for large memory allocations
Date: Fri, 28 Feb 2014 16:54:34 +0800 [thread overview]
Message-ID: <53104ECA.4010702@freescale.com> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D102844605F38C@CNBJMBX05.corpusers.net>
于 2014年02月28日 16:15, Wang, Yalin 写道:
> could this module change the memory allocation into vmalloc ?
the buffer allocated by vmalloc can not be used for the DMA.
I think that's why drivers use the kmalloc.
thanks
Huang Shijie
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-02-28 8:54 UTC|newest]
Thread overview: 25+ 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 [this message]
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 ` [alsa-devel] " Mark Brown
2014-02-28 8:15 Wang, Yalin
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=53104ECA.4010702@freescale.com \
--to=b32955@freescale.com \
--cc='gregkh@linuxfoundation.org \
--cc=Yalin.Wang@sonymobile.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=coreteam@netfilter.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mingo@redhat.com \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=perex@perex.cz \
--cc=rostedt@goodmis.org \
--cc=rydberg@euromail.se \
--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;
as well as URLs for NNTP newsgroup(s).