From: Andrew Morton <akpm@linux-foundation.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Save some bytes in mm_struct by filling holes on 64bit
Date: Wed, 12 Mar 2008 11:05:37 -0700 [thread overview]
Message-ID: <20080312110537.3f812130.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080312142807.GA2290@bingen.suse.de>
On Wed, 12 Mar 2008 15:28:07 +0100 Andi Kleen <ak@suse.de> wrote:
>
> Save some bytes in mm_struct by filling holes
>
> Putting int values together for better packing on 64bit
> shrinks sizeof(struct mm_struct) from 776 bytes to 760 bytes.
>
> Signed-off-by: Andi Kleen <ak@suse.de>
>
> Index: linux-2.6.25-rc5/include/linux/mm_types.h
> ===================================================================
> --- linux-2.6.25-rc5.orig/include/linux/mm_types.h
> +++ linux-2.6.25-rc5/include/linux/mm_types.h
> @@ -172,6 +172,7 @@ struct mm_struct {
> atomic_t mm_users; /* How many users with user space? */
> atomic_t mm_count; /* How many references to "struct mm_struct" (users count as 1) */
> int map_count; /* number of VMAs */
> + rwlock_t ioctx_list_lock; /* aio lock */
> struct rw_semaphore mmap_sem;
> spinlock_t page_table_lock; /* Protects page tables and some counters */
>
> @@ -213,14 +214,13 @@ struct mm_struct {
> unsigned int token_priority;
> unsigned int last_interval;
>
> + int core_waiters;
> unsigned long flags; /* Must use atomic bitops to access the bits */
>
> /* coredumping support */
> - int core_waiters;
> struct completion *core_startup_done, core_done;
>
> /* aio bits */
> - rwlock_t ioctx_list_lock;
> struct kioctx *ioctx_list;
> #ifdef CONFIG_CGROUP_MEM_RES_CTLR
> struct mem_cgroup *mem_cgroup;
The current ioctx_list_lock position is better from a cache layout POV?
next prev parent reply other threads:[~2008-03-12 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 14:28 [PATCH] Save some bytes in mm_struct by filling holes on 64bit Andi Kleen
2008-03-12 18:05 ` Andrew Morton [this message]
2008-03-12 18:38 ` Andi Kleen
2008-03-13 16:40 ` Lennart Sorensen
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=20080312110537.3f812130.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--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