From: Eric Dumazet <dada1@cosmosbay.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] remove unused blkp field in percpu_data
Date: Sat, 03 Dec 2005 02:15:46 +0100 [thread overview]
Message-ID: <4390F1C2.7080602@cosmosbay.com> (raw)
In-Reply-To: <438C7218.8030109@cosmosbay.com>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
[PATCH] remove unused blkp field in percpu_data
I found that blkp field was not used in kernel tree.
As most of the times NR_CPUS is a power of two and kmalloc() memory blocks
too, this extra field basically doubles the memory space allocated in
__alloc_percpu() to store the 'struct percpu_data'
(for example, if NR_CPUS=8 on i386, kmalloc(4*8+4) returns a 64 bytes block
instead of a 32 bytes block after this patch)
Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
[-- Attachment #2: percpu_data.patch --]
[-- Type: text/plain, Size: 231 bytes --]
--- linux-2.6/include/linux/percpu.h 2005-11-29 04:51:27.000000000 +0100
+++ linux-2.6-ed/linux/percpu.h 2005-12-03 01:57:23.000000000 +0100
@@ -19,7 +19,6 @@
struct percpu_data {
void *ptrs[NR_CPUS];
- void *blkp;
};
/*
next prev parent reply other threads:[~2005-12-03 1:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 7:17 [PATCH] race condition in procfs Grzegorz Nosek
2005-11-29 8:09 ` Andrew Morton
2005-11-29 8:38 ` Grzegorz Nosek
2005-11-29 13:25 ` Grzegorz Nosek
2005-11-29 14:04 ` Grzegorz Nosek
2005-11-29 14:28 ` Steven Rostedt
2005-11-29 14:39 ` Grzegorz Nosek
2005-11-29 14:49 ` Steven Rostedt
2005-11-30 14:41 ` Grzegorz Nosek
2005-11-30 15:14 ` Steven Rostedt
2005-11-30 15:29 ` Grzegorz Nosek
2005-11-30 16:25 ` Steven Rostedt
2005-11-30 17:23 ` Grzegorz Nosek
2005-12-01 20:38 ` Grzegorz Nosek
2005-11-29 15:22 ` [PATCH] shrinks dentry struct Eric Dumazet
2005-11-30 2:06 ` Paul Jackson
2005-11-30 2:14 ` Andrew Morton
2005-11-30 2:43 ` Paul Jackson
2005-11-30 6:56 ` Hugh Dickins
2005-12-03 1:15 ` Eric Dumazet [this message]
2005-12-13 18:03 ` Paul E. McKenney
2005-12-13 18:24 ` Eric Dumazet
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=4390F1C2.7080602@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox