From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: dada1@cosmosbay.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] shrinks dentry struct
Date: Tue, 29 Nov 2005 18:14:21 -0800 [thread overview]
Message-ID: <20051129181421.0e273d83.akpm@osdl.org> (raw)
In-Reply-To: <20051129180653.f8d40e9a.pj@sgi.com>
Paul Jackson <pj@sgi.com> wrote:
>
> Would the following accomplish the same thing as your patch, to shrink
> UP dentry structs back to 128 bytes, with a smaller and less intrusive
> patch?
>
> ...
> - struct list_head d_child; /* child of parent list */
> + union { /* Fit 32 bit UP dentry in 128 bytes */
> + struct list_head du_child; /* child of parent list */
> + struct rcu_head du_rcu;
> + } d_du;
> ...
>
> +#define d_child d_du.du_child
> +#define d_rcu d_du.du_rcu
Yes, but it's better to just do the big edit, rather than letting these
little namespace crufties accumulate over time.
Even better would be to ditch gcc-2.95.x and use an anonymous union, but
Hugh won't let me ;)
next prev parent reply other threads:[~2005-11-30 2:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 7:17 [PATCH] race condition in procfs Grzegorz Nosek
2005-11-29 8:09 ` Andrew Morton
2005-11-29 8:38 ` Grzegorz Nosek
2005-11-29 13:25 ` Grzegorz Nosek
2005-11-29 14:04 ` Grzegorz Nosek
2005-11-29 14:28 ` Steven Rostedt
2005-11-29 14:39 ` Grzegorz Nosek
2005-11-29 14:49 ` Steven Rostedt
2005-11-30 14:41 ` Grzegorz Nosek
2005-11-30 15:14 ` Steven Rostedt
2005-11-30 15:29 ` Grzegorz Nosek
2005-11-30 16:25 ` Steven Rostedt
2005-11-30 17:23 ` Grzegorz Nosek
2005-12-01 20:38 ` Grzegorz Nosek
2005-11-29 15:22 ` [PATCH] shrinks dentry struct Eric Dumazet
2005-11-30 2:06 ` Paul Jackson
2005-11-30 2:14 ` Andrew Morton [this message]
2005-11-30 2:43 ` Paul Jackson
2005-11-30 6:56 ` Hugh Dickins
2005-12-03 1:15 ` [PATCH] remove unused blkp field in percpu_data Eric Dumazet
2005-12-13 18:03 ` [PATCH] shrinks dentry struct Paul E. McKenney
2005-12-13 18:24 ` Eric Dumazet
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=20051129181421.0e273d83.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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®