From: Andi Kleen <ak@suse.de>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: ak@suse.de, linux-mm@kvack.org
Subject: Re: [patch] CONFIG_ARCH_HAS_ATOMIC_UNSIGNED
Date: Fri, 17 Dec 2004 07:11:51 +0100 [thread overview]
Message-ID: <20041217061150.GF12049@wotan.suse.de> (raw)
In-Reply-To: <E1Cf6EG-00015y-00@kernel.beaverton.ibm.com>
On Thu, Dec 16, 2004 at 04:44:20PM -0800, Dave Hansen wrote:
>
> This reduces another one of the dependencies that struct page's
> definition has on any arch-specific header files. Currently,
> only x86_64 uses this, so it's the only architecture that needed
> to be modified.
That's for page_flags_t, right?
I think it could be dropped right now and just use unsigned long for flags again.
Since the objrmap work the saved 4 bytes in struct page are wasted in padding
and I haven't found a way to use them for real space saving again
because all other members are 8 byte or paired 4 byte.
Of course if anybody could come up with a way to make struct page
smaller it would be very appreciated:
struct page {
page_flags_t flags; /* Atomic flags, some possibly
* updated asynchronously */
<------------ what to do with the 4 byte padding here?
atomic_t _count; /* Usage count, see below. */
atomic_t _mapcount; /* Count of ptes mapped in mms,
* to show when page is mapped
* & limit reverse map searches.
*/
unsigned long private; /* Mapping-private opaque data:
* usually used for buffer_heads
* if PagePrivate set; used for
* swp_entry_t if PageSwapCache
*/
struct address_space *mapping; /* If low bit clear, points to
* inode address_space, or NULL.
* If page mapped as anonymous
* memory, low bit is set, and
* it points to anon_vma object:
* see PAGE_MAPPING_ANON below.
*/
pgoff_t index; /* Our offset within mapping. */
struct list_head lru; /* Pageout list, eg. active_list
* protected by zone->lru_lock !
*/
-Andi
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-12-17 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 0:44 Dave Hansen
2004-12-17 6:11 ` Andi Kleen [this message]
2004-12-17 8:42 ` Dave Hansen
2004-12-17 16:27 ` Christoph Lameter
2004-12-17 16:33 ` Andi Kleen
2004-12-17 19:26 ` Christoph Lameter
2004-12-17 19:37 ` Andi Kleen
2004-12-17 22:11 ` Christoph Lameter
2004-12-18 6:50 ` Andi Kleen
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=20041217061150.GF12049@wotan.suse.de \
--to=ak@suse.de \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.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