From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 3/7] sanitize xlog_in_core_t definition
Date: Tue, 28 Oct 2008 16:17:34 +1100 [thread overview]
Message-ID: <20081028051734.GC17077@disturbed> (raw)
In-Reply-To: <20081027133907.GD1109@infradead.org>
On Mon, Oct 27, 2008 at 09:39:07AM -0400, Christoph Hellwig wrote:
> Move all fields from xlog_iclog_fields_t into xlog_in_core_t instead of having
> them in a substructure and the using #defines to make it look like they were
> directly in xlog_in_core_t. Also document that xlog_in_core_2_t is grossly
> misnamed, and make all references to it typesafe.
>
> (First sent on Semptember 15th)
Couple of things.
> @@ -361,41 +371,11 @@ typedef struct xlog_iclog_fields {
>
> /* reference counts need their own cacheline */
> atomic_t ic_refcnt ____cacheline_aligned_in_smp;
> -} xlog_iclog_fields_t;
> -
> -typedef union xlog_in_core2 {
> - xlog_rec_header_t hic_header;
> - xlog_rec_ext_header_t hic_xheader;
> - char hic_sector[XLOG_HEADER_SIZE];
> -} xlog_in_core_2_t;
> -
> -typedef struct xlog_in_core {
> - xlog_iclog_fields_t hic_fields;
> - xlog_in_core_2_t *hic_data;
> + xlog_in_core_2_t *ic_data;
> +#define ic_header ic_data->hic_header
> } xlog_in_core_t;
The ic_data pointer should not be on the same cacheline as the
reference count seeing as it is read-only field.
Otherwise seems ok.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-10-28 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 13:39 [PATCH 3/7] sanitize xlog_in_core_t definition Christoph Hellwig
2008-10-28 5:17 ` Dave Chinner [this message]
2008-10-28 9:16 ` Christoph Hellwig
2008-10-28 21:51 ` Dave Chinner
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=20081028051734.GC17077@disturbed \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.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