From: Qiang Huang <h.huangqiang@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>,
cl@linux-foundation.org, penberg@kernel.org, mpm@selenic.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] slab: remove the redundant declaration of kmalloc
Date: Fri, 22 Nov 2013 09:07:10 +0800 [thread overview]
Message-ID: <528EAE3E.5080604@huawei.com> (raw)
In-Reply-To: <528E5AEF.6020007@infradead.org>
On 2013/11/22 3:11, Randy Dunlap wrote:
> On 11/20/13 21:57, Qiang Huang wrote:
>>
>> Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
>
> or use my patch from 2013-09-17:
> http://marc.info/?l=linux-mm&m=137944291611467&w=2
>
> Would be nice to one of these merged...
Yes, sorry for not notice this, merge your patch should be property :)
But why it's still not be merged?
Ping...
>
>
>> ---
>> include/linux/slab.h | 102 +++++++++++++++++++++++----------------------------
>> 1 file changed, 46 insertions(+), 56 deletions(-)
>>
>> diff --git a/include/linux/slab.h b/include/linux/slab.h
>> index 74f1058..630f22f 100644
>> --- a/include/linux/slab.h
>> +++ b/include/linux/slab.h
>> @@ -381,7 +381,52 @@ static __always_inline void *kmalloc_large(size_t size, gfp_t flags)
>> /**
>> * kmalloc - allocate memory
>> * @size: how many bytes of memory are required.
>> - * @flags: the type of memory to allocate (see kcalloc).
>> + * @flags: the type of memory to allocate.
>> + *
>> + * The @flags argument may be one of:
>> + *
>> + * %GFP_USER - Allocate memory on behalf of user. May sleep.
>> + *
>> + * %GFP_KERNEL - Allocate normal kernel ram. May sleep.
>> + *
>> + * %GFP_ATOMIC - Allocation will not sleep. May use emergency pools.
>> + * For example, use this inside interrupt handlers.
>> + *
>> + * %GFP_HIGHUSER - Allocate pages from high memory.
>> + *
>> + * %GFP_NOIO - Do not do any I/O at all while trying to get memory.
>> + *
>> + * %GFP_NOFS - Do not make any fs calls while trying to get memory.
>> + *
>> + * %GFP_NOWAIT - Allocation will not sleep.
>> + *
>> + * %GFP_THISNODE - Allocate node-local memory only.
>> + *
>> + * %GFP_DMA - Allocation suitable for DMA.
>> + * Should only be used for kmalloc() caches. Otherwise, use a
>> + * slab created with SLAB_DMA.
>> + *
>> + * Also it is possible to set different flags by OR'ing
>> + * in one or more of the following additional @flags:
>> + *
>> + * %__GFP_COLD - Request cache-cold pages instead of
>> + * trying to return cache-warm pages.
>> + *
>> + * %__GFP_HIGH - This allocation has high priority and may use emergency pools.
>> + *
>> + * %__GFP_NOFAIL - Indicate that this allocation is in no way allowed to fail
>> + * (think twice before using).
>> + *
>> + * %__GFP_NORETRY - If memory is not immediately available,
>> + * then give up at once.
>> + *
>> + * %__GFP_NOWARN - If allocation fails, don't issue any warnings.
>> + *
>> + * %__GFP_REPEAT - If allocation fails initially, try once more before failing.
>> + *
>> + * There are other flags available as well, but these are not intended
>> + * for general use, and so are not documented here. For a full list of
>> + * potential flags, always refer to linux/gfp.h.
>> *
>> * kmalloc is the normal method of allocating memory
>> * for objects smaller than page size in the kernel.
>> @@ -495,61 +540,6 @@ int cache_show(struct kmem_cache *s, struct seq_file *m);
>> void print_slabinfo_header(struct seq_file *m);
>>
>> /**
>> - * kmalloc - allocate memory
>> - * @size: how many bytes of memory are required.
>> - * @flags: the type of memory to allocate.
>> - *
>> - * The @flags argument may be one of:
>> - *
>> - * %GFP_USER - Allocate memory on behalf of user. May sleep.
>> - *
>> - * %GFP_KERNEL - Allocate normal kernel ram. May sleep.
>> - *
>> - * %GFP_ATOMIC - Allocation will not sleep. May use emergency pools.
>> - * For example, use this inside interrupt handlers.
>> - *
>> - * %GFP_HIGHUSER - Allocate pages from high memory.
>> - *
>> - * %GFP_NOIO - Do not do any I/O at all while trying to get memory.
>> - *
>> - * %GFP_NOFS - Do not make any fs calls while trying to get memory.
>> - *
>> - * %GFP_NOWAIT - Allocation will not sleep.
>> - *
>> - * %GFP_THISNODE - Allocate node-local memory only.
>> - *
>> - * %GFP_DMA - Allocation suitable for DMA.
>> - * Should only be used for kmalloc() caches. Otherwise, use a
>> - * slab created with SLAB_DMA.
>> - *
>> - * Also it is possible to set different flags by OR'ing
>> - * in one or more of the following additional @flags:
>> - *
>> - * %__GFP_COLD - Request cache-cold pages instead of
>> - * trying to return cache-warm pages.
>> - *
>> - * %__GFP_HIGH - This allocation has high priority and may use emergency pools.
>> - *
>> - * %__GFP_NOFAIL - Indicate that this allocation is in no way allowed to fail
>> - * (think twice before using).
>> - *
>> - * %__GFP_NORETRY - If memory is not immediately available,
>> - * then give up at once.
>> - *
>> - * %__GFP_NOWARN - If allocation fails, don't issue any warnings.
>> - *
>> - * %__GFP_REPEAT - If allocation fails initially, try once more before failing.
>> - *
>> - * There are other flags available as well, but these are not intended
>> - * for general use, and so are not documented here. For a full list of
>> - * potential flags, always refer to linux/gfp.h.
>> - *
>> - * kmalloc is the normal method of allocating memory
>> - * in the kernel.
>> - */
>> -static __always_inline void *kmalloc(size_t size, gfp_t flags);
>> -
>> -/**
>> * kmalloc_array - allocate memory for an array.
>> * @n: number of elements.
>> * @size: element size.
>>
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Qiang Huang <h.huangqiang@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>, <cl@linux-foundation.org>,
<penberg@kernel.org>, <mpm@selenic.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] slab: remove the redundant declaration of kmalloc
Date: Fri, 22 Nov 2013 09:07:10 +0800 [thread overview]
Message-ID: <528EAE3E.5080604@huawei.com> (raw)
In-Reply-To: <528E5AEF.6020007@infradead.org>
On 2013/11/22 3:11, Randy Dunlap wrote:
> On 11/20/13 21:57, Qiang Huang wrote:
>>
>> Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
>
> or use my patch from 2013-09-17:
> http://marc.info/?l=linux-mm&m=137944291611467&w=2
>
> Would be nice to one of these merged...
Yes, sorry for not notice this, merge your patch should be property :)
But why it's still not be merged?
Ping...
>
>
>> ---
>> include/linux/slab.h | 102 +++++++++++++++++++++++----------------------------
>> 1 file changed, 46 insertions(+), 56 deletions(-)
>>
>> diff --git a/include/linux/slab.h b/include/linux/slab.h
>> index 74f1058..630f22f 100644
>> --- a/include/linux/slab.h
>> +++ b/include/linux/slab.h
>> @@ -381,7 +381,52 @@ static __always_inline void *kmalloc_large(size_t size, gfp_t flags)
>> /**
>> * kmalloc - allocate memory
>> * @size: how many bytes of memory are required.
>> - * @flags: the type of memory to allocate (see kcalloc).
>> + * @flags: the type of memory to allocate.
>> + *
>> + * The @flags argument may be one of:
>> + *
>> + * %GFP_USER - Allocate memory on behalf of user. May sleep.
>> + *
>> + * %GFP_KERNEL - Allocate normal kernel ram. May sleep.
>> + *
>> + * %GFP_ATOMIC - Allocation will not sleep. May use emergency pools.
>> + * For example, use this inside interrupt handlers.
>> + *
>> + * %GFP_HIGHUSER - Allocate pages from high memory.
>> + *
>> + * %GFP_NOIO - Do not do any I/O at all while trying to get memory.
>> + *
>> + * %GFP_NOFS - Do not make any fs calls while trying to get memory.
>> + *
>> + * %GFP_NOWAIT - Allocation will not sleep.
>> + *
>> + * %GFP_THISNODE - Allocate node-local memory only.
>> + *
>> + * %GFP_DMA - Allocation suitable for DMA.
>> + * Should only be used for kmalloc() caches. Otherwise, use a
>> + * slab created with SLAB_DMA.
>> + *
>> + * Also it is possible to set different flags by OR'ing
>> + * in one or more of the following additional @flags:
>> + *
>> + * %__GFP_COLD - Request cache-cold pages instead of
>> + * trying to return cache-warm pages.
>> + *
>> + * %__GFP_HIGH - This allocation has high priority and may use emergency pools.
>> + *
>> + * %__GFP_NOFAIL - Indicate that this allocation is in no way allowed to fail
>> + * (think twice before using).
>> + *
>> + * %__GFP_NORETRY - If memory is not immediately available,
>> + * then give up at once.
>> + *
>> + * %__GFP_NOWARN - If allocation fails, don't issue any warnings.
>> + *
>> + * %__GFP_REPEAT - If allocation fails initially, try once more before failing.
>> + *
>> + * There are other flags available as well, but these are not intended
>> + * for general use, and so are not documented here. For a full list of
>> + * potential flags, always refer to linux/gfp.h.
>> *
>> * kmalloc is the normal method of allocating memory
>> * for objects smaller than page size in the kernel.
>> @@ -495,61 +540,6 @@ int cache_show(struct kmem_cache *s, struct seq_file *m);
>> void print_slabinfo_header(struct seq_file *m);
>>
>> /**
>> - * kmalloc - allocate memory
>> - * @size: how many bytes of memory are required.
>> - * @flags: the type of memory to allocate.
>> - *
>> - * The @flags argument may be one of:
>> - *
>> - * %GFP_USER - Allocate memory on behalf of user. May sleep.
>> - *
>> - * %GFP_KERNEL - Allocate normal kernel ram. May sleep.
>> - *
>> - * %GFP_ATOMIC - Allocation will not sleep. May use emergency pools.
>> - * For example, use this inside interrupt handlers.
>> - *
>> - * %GFP_HIGHUSER - Allocate pages from high memory.
>> - *
>> - * %GFP_NOIO - Do not do any I/O at all while trying to get memory.
>> - *
>> - * %GFP_NOFS - Do not make any fs calls while trying to get memory.
>> - *
>> - * %GFP_NOWAIT - Allocation will not sleep.
>> - *
>> - * %GFP_THISNODE - Allocate node-local memory only.
>> - *
>> - * %GFP_DMA - Allocation suitable for DMA.
>> - * Should only be used for kmalloc() caches. Otherwise, use a
>> - * slab created with SLAB_DMA.
>> - *
>> - * Also it is possible to set different flags by OR'ing
>> - * in one or more of the following additional @flags:
>> - *
>> - * %__GFP_COLD - Request cache-cold pages instead of
>> - * trying to return cache-warm pages.
>> - *
>> - * %__GFP_HIGH - This allocation has high priority and may use emergency pools.
>> - *
>> - * %__GFP_NOFAIL - Indicate that this allocation is in no way allowed to fail
>> - * (think twice before using).
>> - *
>> - * %__GFP_NORETRY - If memory is not immediately available,
>> - * then give up at once.
>> - *
>> - * %__GFP_NOWARN - If allocation fails, don't issue any warnings.
>> - *
>> - * %__GFP_REPEAT - If allocation fails initially, try once more before failing.
>> - *
>> - * There are other flags available as well, but these are not intended
>> - * for general use, and so are not documented here. For a full list of
>> - * potential flags, always refer to linux/gfp.h.
>> - *
>> - * kmalloc is the normal method of allocating memory
>> - * in the kernel.
>> - */
>> -static __always_inline void *kmalloc(size_t size, gfp_t flags);
>> -
>> -/**
>> * kmalloc_array - allocate memory for an array.
>> * @n: number of elements.
>> * @size: element size.
>>
>
>
next prev parent reply other threads:[~2013-11-22 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 5:57 [PATCH] slab: remove the redundant declaration of kmalloc Qiang Huang
2013-11-21 5:57 ` Qiang Huang
2013-11-21 19:11 ` Randy Dunlap
2013-11-21 19:11 ` Randy Dunlap
2013-11-22 1:07 ` Qiang Huang [this message]
2013-11-22 1:07 ` Qiang Huang
2013-11-23 2:10 ` Randy Dunlap
2013-11-23 2:10 ` Randy Dunlap
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=528EAE3E.5080604@huawei.com \
--to=h.huangqiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=rdunlap@infradead.org \
/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.