public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: akpm@digeo.com
Cc: willy@debian.org, ak@muc.de, linux-kernel@vger.kernel.org,
	anton@samba.org, schwidefsky@de.ibm.com, davidm@hpl.hp.com,
	matthew@wil.cx, ralf@linux-mips.org, rth@redhat.com
Subject: Re: Reduce struct page by 8 bytes on 64bit
Date: Wed, 16 Apr 2003 14:40:35 -0700 (PDT)	[thread overview]
Message-ID: <20030416.144035.130217416.davem@redhat.com> (raw)
In-Reply-To: <20030416144311.46f32253.akpm@digeo.com>

   From: Andrew Morton <akpm@digeo.com>
   Date: Wed, 16 Apr 2003 14:43:11 -0700
   
   Well are we sure that the `flags' and `count' fields will always fall into
   the same 256-byte range?  Wouldn't it subtly break if sizeof(struct page)
   became not a multiple of eight?  Will the compiler pad it out anyway?

As long as there is a long or pointer member, the structure
will be required to be 8 byte or better aligned.

  reply	other threads:[~2003-04-16 21:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 11:24 Reduce struct page by 8 bytes on 64bit Andi Kleen
2003-04-16 12:45 ` David S. Miller
2003-04-16 13:22   ` Jakub Jelinek
2003-04-16 14:07   ` Andi Kleen
2003-04-16 14:26     ` David S. Miller
2003-04-16 14:43       ` Andi Kleen
2003-04-16 14:38         ` David S. Miller
2003-04-16 14:58           ` Andi Kleen
2003-04-16 14:58             ` David S. Miller
2003-04-16 14:55         ` Matthew Wilcox
2003-04-16 15:04           ` Andi Kleen
2003-04-16 15:00             ` David S. Miller
2003-04-16 15:11             ` Matthew Wilcox
2003-04-16 20:35               ` Andrew Morton
2003-04-16 21:26                 ` Matthew Wilcox
2003-04-16 21:43                   ` Andrew Morton
2003-04-16 21:40                     ` David S. Miller [this message]
2003-04-17 15:20                       ` 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=20030416.144035.130217416.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=anton@samba.org \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=ralf@linux-mips.org \
    --cc=rth@redhat.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=willy@debian.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