From: akpm@linux-foundation.org
To: jj@chaosbits.net, karim@opersys.com, lethal@linux-sh.org,
mathieu.desnoyers@polymtl.ca, zanussi@us.ibm.com,
mm-commits@vger.kernel.org
Subject: [merged] kernel-relayc-relay_alloc_page_array-use-vzalloc.patch removed from -mm tree
Date: Mon, 08 Nov 2010 12:01:32 -0800 [thread overview]
Message-ID: <201011082003.oA8K3eWD005379@imap1.linux-foundation.org> (raw)
The patch titled
kernel/relay.c: relay_alloc_page_array() use vzalloc()
has been removed from the -mm tree. Its filename was
kernel-relayc-relay_alloc_page_array-use-vzalloc.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: kernel/relay.c: relay_alloc_page_array() use vzalloc()
From: Jesper Juhl <jj@chaosbits.net>
We can optimize kernel/relay.c::relay_alloc_page_array() slightly by using
vzalloc. The patch makes these changes:
- use vzalloc instead of vmalloc+memset.
- remove redundant local variable 'array'.
- declare local 'pa_size' as const.
Cuts down nicely on both source and object-code size.
Signed-off-by: Jesper Juhl <jj@chaosbits.net>
Cc: Tom Zanussi <zanussi@us.ibm.com>
Cc: Karim Yaghmour <karim@opersys.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/relay.c | 15 ++++-----------
1 file changed, 4 insertions(+), 11 deletions(-)
diff -puN kernel/relay.c~kernel-relayc-relay_alloc_page_array-use-vzalloc kernel/relay.c
--- a/kernel/relay.c~kernel-relayc-relay_alloc_page_array-use-vzalloc
+++ a/kernel/relay.c
@@ -70,17 +70,10 @@ static const struct vm_operations_struct
*/
static struct page **relay_alloc_page_array(unsigned int n_pages)
{
- struct page **array;
- size_t pa_size = n_pages * sizeof(struct page *);
reply other threads:[~2010-11-08 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201011082003.oA8K3eWD005379@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jj@chaosbits.net \
--cc=karim@opersys.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mm-commits@vger.kernel.org \
--cc=zanussi@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.