All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <christoph@lameter.com>
Cc: Andi Kleen <ak@suse.de>, Dave Hansen <haveblue@us.ibm.com>,
	linux-mm@kvack.org
Subject: Re: [patch] CONFIG_ARCH_HAS_ATOMIC_UNSIGNED
Date: Fri, 17 Dec 2004 17:33:08 +0100	[thread overview]
Message-ID: <20041217163308.GE14229@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0412170827280.17806@server.graphe.net>

On Fri, Dec 17, 2004 at 08:27:58AM -0800, Christoph Lameter wrote:
> 
> On Fri, 17 Dec 2004, Andi Kleen wrote:
> 
> > struct page {
> >         page_flags_t flags;             /* Atomic flags, some possibly
> >                                          * updated asynchronously */
> >
> > 			<------------ what to do with the 4 byte padding here?
> >
> 
> 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.

Also what's the problem of having it in index?

-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>

  reply	other threads:[~2004-12-17 16:33 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 [this message]
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=20041217163308.GE14229@wotan.suse.de \
    --to=ak@suse.de \
    --cc=christoph@lameter.com \
    --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.