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 11:26:49 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0412171118430.20902@server.graphe.net> (raw)
In-Reply-To: <20041217163308.GE14229@wotan.suse.de>
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.
> Also what's the problem of having it in index?
It implies that huge pages cannot be handled in the same way as regular
pages. F.e. if huge pages should ever be able to map files then huge
pages will also need page->index. Maybe its best to encode the order in
a 64 bit page flags on 64 bit machines? It will be zero in most cases and
one could then simply check for having a hugepage and get to the first page
without a pointer if the huge pages are properly aligned in their address
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 19:26 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
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 [this message]
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=Pine.LNX.4.58.0412171118430.20902@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox