From: Christoph Lameter <christoph@lameter.com>
To: Andi Kleen <ak@suse.de>
Cc: Dave Hansen <haveblue@us.ibm.com>, linux-mm@kvack.org
Subject: Re: [patch] CONFIG_ARCH_HAS_ATOMIC_UNSIGNED
Date: Fri, 17 Dec 2004 14:11:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0412171410240.23925@server.graphe.net> (raw)
In-Reply-To: <20041217193724.GA13542@wotan.suse.de>
On Fri, 17 Dec 2004, Andi Kleen wrote:
> On Fri, Dec 17, 2004 at 11:26:49AM -0800, Christoph Lameter wrote:
> > On Fri, 17 Dec 2004, Andi Kleen wrote:
> >
> > > > Put the order of the page there for compound pages instead of having that
> > > > in index?
> > >
> > > That would waste memory on the 64bit architectures that cannot tolerate
> > > 32bit atomic flags or on true 32bit architecture.
> >
> > Would be great to have 64 bit atomic support to fill this hole then.
>
> I think you lost me. How would that help?
It would fill the hole on 64 bits if atomic_t would have the native word
size.
> To fill the hole you would need a 4 byte member with padding to move around,
> but there isn't one. You cannot also just add one because it would waste
> memory on 32bit archs and other 64bit archs.
There is no clean solution here but I just wanted to indicate what I would
like to see there if you want to use the space.
--
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 22:11 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
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 [this message]
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=Pine.LNX.4.58.0412171410240.23925@server.graphe.net \
--to=christoph@lameter.com \
--cc=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 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.