From: Dave Hansen <haveblue@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-mm <linux-mm@kvack.org>, Andy Wihitcroft <apw@shadowen.org>,
Matthew E Tolentino <matthew.e.tolentino@intel.com>
Subject: Re: [patch] CONFIG_ARCH_HAS_ATOMIC_UNSIGNED
Date: Fri, 17 Dec 2004 00:42:40 -0800 [thread overview]
Message-ID: <1103272960.13614.3084.camel@localhost> (raw)
In-Reply-To: <20041217061150.GF12049@wotan.suse.de>
On Thu, 2004-12-16 at 22:11, Andi Kleen wrote:
> 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?
Yep.
> I think it could be dropped right now and just use unsigned long for
> flags again.
That's fine with me (and a much simpler patch).
> 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.
Well, since you asked... :)
In a newer revision of the nonlinear code, Andy Whitcroft has decided to
store part of the page_to_pfn() translation directly in page->flags,
right next to the zone information. This is a bit of a squeeze on
32-bit arches, but on the 64-bit ones, there's plenty of room since
nobody is using the upper 32 bits at all.
I didn't realize that x86_64 had a 32-bit type there, so we probably
would have suggested turning it into a 64-bit one eventually.
-- Dave
--
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 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 0:44 [patch] CONFIG_ARCH_HAS_ATOMIC_UNSIGNED Dave Hansen
2004-12-17 6:11 ` Andi Kleen
2004-12-17 8:42 ` Dave Hansen [this message]
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=1103272960.13614.3084.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=ak@suse.de \
--cc=apw@shadowen.org \
--cc=linux-mm@kvack.org \
--cc=matthew.e.tolentino@intel.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.