From: Benjamin Blum <bblum@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, akpm@linux-foundation.org,
serue@us.ibm.com, menage@google.com
Subject: Re: [PATCH 3/3] Quick vmalloc vs kmalloc fix to the case where array size is too large
Date: Mon, 13 Jul 2009 11:27:43 -0400 [thread overview]
Message-ID: <2f86c2480907130827u7d2b062bw26bbb80a8e3de657@mail.gmail.com> (raw)
In-Reply-To: <20090713150303.70ab5176.kamezawa.hiroyu@jp.fujitsu.com>
On Mon, Jul 13, 2009 at 2:03 AM, KAMEZAWA
Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> ???? why not using vmalloc() always ?
>
> Thanks,
> -Kame
>
The idea behind this patch is that in most cases, we want to use
kmalloc for performance, but sometimes the array will be too big. See
the previous thread (linked in the root message of this thread) for
discussion of the issue.
next prev parent reply other threads:[~2009-07-13 15:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 23:01 [PATCH v2 0/3] CGroups: cgroup member list enhancement/fix Ben Blum
2009-07-10 23:01 ` [PATCH 1/3] Adds a read-only "procs" file similar to "tasks" that shows only unique tgids Ben Blum
2009-07-13 3:46 ` Li Zefan
2009-07-13 15:25 ` Benjamin Blum
2009-07-14 18:34 ` Dave Hansen
2009-07-14 21:26 ` Benjamin Blum
2009-07-14 21:49 ` Dave Hansen
2009-07-14 22:55 ` Benjamin Blum
2009-07-15 1:31 ` Li Zefan
2009-07-10 23:02 ` [PATCH 2/3] Ensures correct concurrent opening/reading of pidlists across pid namespaces Ben Blum
2009-07-11 21:59 ` Serge E. Hallyn
2009-07-10 23:02 ` [PATCH 3/3] Quick vmalloc vs kmalloc fix to the case where array size is too large Ben Blum
2009-07-13 3:03 ` Li Zefan
2009-07-13 6:03 ` KAMEZAWA Hiroyuki
2009-07-13 15:27 ` Benjamin Blum [this message]
2009-07-13 23:49 ` KAMEZAWA Hiroyuki
2009-07-14 3:50 ` Paul Menage
2009-07-14 3:53 ` KAMEZAWA Hiroyuki
2009-07-14 4:04 ` Paul Menage
2009-07-14 4:25 ` KAMEZAWA Hiroyuki
2009-07-14 17:26 ` Benjamin Blum
2009-07-14 17:28 ` Paul Menage
2009-07-14 17:47 ` Dave Hansen
2009-07-14 17:50 ` Paul Menage
2009-07-14 21:30 ` Benjamin Blum
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=2f86c2480907130827u7d2b062bw26bbb80a8e3de657@mail.gmail.com \
--to=bblum@google.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=serue@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®