From: Hugh Dickins <hugh@veritas.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Mikael Starvik <mikael.starvik@axis.com>,
akpm@osdl.org, andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shrink rbtree
Date: Sun, 23 Apr 2006 14:03:15 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0604231359350.3678@blonde.wat.veritas.com> (raw)
In-Reply-To: <1145657573.11909.226.camel@pmac.infradead.org>
On Fri, 21 Apr 2006, David Woodhouse wrote:
> On Fri, 2006-04-21 at 21:57 +0100, Hugh Dickins wrote:
> >
> > You can often get away with it - I notice we never added the same
> > alignment to struct anon_vma, which in theory needed it just as much.
> > Some accident of how structures are packed into slabs on CRIS, I suppose.
>
> That sounds very strange to me, but it's harmless enough to add the
> explicit alignment.
It's occurred to me that the unusual thing about struct address_space
is that it does _not_ have a slab cache of its own: it's for years been
part of the struct inode itself; and I guess that exposes it to an
alignment issue which slab objects themselves avoid. But still a
good idea to add the explicit alignment as doc.
Hugh
next prev parent reply other threads:[~2006-04-23 13:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 12:47 David Woodhouse
2006-04-21 13:06 ` Nick Piggin
2006-04-21 19:08 ` David Woodhouse
2006-04-21 20:57 ` Hugh Dickins
2006-04-21 22:12 ` David Woodhouse
2006-04-23 13:03 ` Hugh Dickins [this message]
2006-04-21 18:24 ` Zach Brown
2006-04-21 19:06 ` David Woodhouse
2006-04-21 19:25 ` Zach Brown
2006-04-22 1:09 ` Andrew Morton
2006-04-22 1:10 ` Andrew Morton
2006-04-22 1:21 ` Andrew Morton
2006-04-22 1:29 ` David Woodhouse
2006-04-22 12:29 ` Ingo Oeser
2006-04-22 13:38 ` David Woodhouse
2006-04-22 22:55 ` Ingo Oeser
2006-04-23 16:36 ` Steven Rostedt
2006-04-23 17:20 ` Thomas Gleixner
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.64.0604231359350.3678@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.com \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®