All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Ben Blum <bblum@google.com>
Cc: 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:03:03 +0800	[thread overview]
Message-ID: <4A5AA3E7.9070800@cn.fujitsu.com> (raw)
In-Reply-To: <20090710230205.16778.11707.stgit@hastromil.mtv.corp.google.com>

Ben Blum wrote:
> Quick vmalloc vs kmalloc fix to the case where array size is too large
> 
> Separates all pidlist allocation requests to a separate function that judges
> based on the requested size whether or not the array needs to be vmalloced or
> can be gotten via kmalloc, and similar for kfree/vfree. Should be replaced
> entirely with a kernel-wide solution to this general problem.
> 
> Depends on cgroup-pidlist-namespace.patch, cgroup-procs.patch
> 

Since this is a patchset, you don't need to tell the dependencies of
this patch, at least not in changelog, but can put it ...

> Signed-off-by: Ben Blum <bblum@google.com>
> 
> ---
> 

... here

---  <- followed by this mark

>  kernel/cgroup.c |   34 ++++++++++++++++++++++++++++------
>  1 files changed, 28 insertions(+), 6 deletions(-)
> 
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index 33d89be..0ed85fa 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -48,6 +48,7 @@
>  #include <linux/namei.h>
>  #include <linux/smp_lock.h>
>  #include <linux/pid_namespace.h>
> +#include <linux/vmalloc.h> /* TODO: replace with more sophisticated array */
>  

Is this TODO different with the below one?

>  #include <asm/atomic.h>
>  
> @@ -2121,6 +2122,27 @@ int cgroup_scan_tasks(struct cgroup_scanner *scan)
>   */
>  
>  /*
> + * The following two functions "fix" the issue where there are more pids
> + * than kmalloc will give memory for; in such cases, we use vmalloc/vfree.
> + * TODO: replace with a kernel-wide solution to this problem
> + */
> +#define PIDLIST_TOO_LARGE(c) ((c) * sizeof(pid_t) > (PAGE_SIZE * 2))

I think order-0 is most robust and should be used as much as possible.

> +static inline void *pidlist_allocate(int count)

It's better to let gcc decide to inline it or not.

> +{
> +	if (PIDLIST_TOO_LARGE(count))
> +		return vmalloc(count * sizeof(pid_t));
> +	else
> +		return kmalloc(count * sizeof(pid_t), GFP_KERNEL);
> +}
> +static inline void pidlist_free(void *p)

ditto

> +{
> +	if (is_vmalloc_addr(p))
> +		vfree(p);
> +	else
> +		kfree(p);
> +}
> +

  parent reply	other threads:[~2009-07-13  3:03 UTC|newest]

Thread overview: 49+ 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 ` Ben Blum
     [not found] ` <20090710230043.16778.29656.stgit-/yCBOHwbXCxd3OlUiQof+WCaruZE5nAUZeezCHUQhQ4@public.gmane.org>
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-10 23:01     ` Ben Blum
2009-07-13  3:46     ` Li Zefan
     [not found]       ` <4A5AAE02.7060106-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-07-13 15:25         ` Benjamin Blum
2009-07-13 15:25       ` Benjamin Blum
     [not found]     ` <20090710230154.16778.58053.stgit-/yCBOHwbXCxd3OlUiQof+WCaruZE5nAUZeezCHUQhQ4@public.gmane.org>
2009-07-13  3:46       ` Li Zefan
2009-07-14 18:34       ` Dave Hansen
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-14 22:55             ` Benjamin Blum
2009-07-15  1:31             ` Li Zefan
2009-07-15  1:31             ` Li Zefan
     [not found]           ` <2f86c2480907141426r16f8ccf3o9770e25cc8d2e509-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-14 21:49             ` Dave Hansen
2009-07-14 21:26         ` Benjamin Blum
2009-07-10 23:02   ` [PATCH 2/3] Ensures correct concurrent opening/reading of pidlists across pid namespaces Ben Blum
2009-07-10 23:02     ` 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-10 23:02     ` Ben Blum
     [not found]     ` <20090710230205.16778.11707.stgit-/yCBOHwbXCxd3OlUiQof+WCaruZE5nAUZeezCHUQhQ4@public.gmane.org>
2009-07-13  3:03       ` Li Zefan
2009-07-13  3:03     ` Li Zefan [this message]
     [not found]       ` <4A5AA3E7.9070800-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-07-13  6:03         ` KAMEZAWA Hiroyuki
2009-07-13  6:03           ` KAMEZAWA Hiroyuki
     [not found]           ` <20090713150303.70ab5176.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-07-13 15:27             ` Benjamin Blum
2009-07-13 15:27           ` Benjamin Blum
2009-07-13 23:49             ` KAMEZAWA Hiroyuki
     [not found]               ` <20090714084950.2401d9a6.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-07-14  3:50                 ` Paul Menage
2009-07-14  3:50                   ` Paul Menage
     [not found]                   ` <6599ad830907132050n226aecb3ucab6746a4d0e81fa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-14  3:53                     ` KAMEZAWA Hiroyuki
2009-07-14  3:53                       ` KAMEZAWA Hiroyuki
     [not found]                       ` <20090714125334.b476aa78.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-07-14  4:04                         ` Paul Menage
2009-07-14  4:04                           ` Paul Menage
     [not found]                           ` <6599ad830907132104o55d31ccexb15e5aa35c31416e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-14  4:25                             ` KAMEZAWA Hiroyuki
2009-07-14  4:25                           ` KAMEZAWA Hiroyuki
2009-07-14 17:26                             ` Benjamin Blum
     [not found]                             ` <20090714132538.ac0bc44a.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-07-14 17:26                               ` Benjamin Blum
2009-07-14 17:28                               ` Paul Menage
2009-07-14 17:28                             ` Paul Menage
     [not found]                               ` <6599ad830907141028y50f36d63h8ea06f73ff369591-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-14 17:47                                 ` Dave Hansen
2009-07-14 17:47                                   ` Dave Hansen
2009-07-14 17:50                                   ` Paul Menage
2009-07-14 17:50                                     ` Paul Menage
     [not found]                                     ` <6599ad830907141050r1e9dde98l56afd37629f749e8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-14 21:30                                       ` Benjamin Blum
2009-07-14 21:30                                         ` Benjamin Blum
     [not found]             ` <2f86c2480907130827u7d2b062bw26bbb80a8e3de657-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-13 23:49               ` KAMEZAWA Hiroyuki

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=4A5AA3E7.9070800@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=bblum@google.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.