From: Andrew Morton <akpm@zip.com.au>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] ext2 synchronous mount speedup
Date: Tue, 12 Feb 2002 16:20:53 -0800 [thread overview]
Message-ID: <3C69B165.4301DD9A@zip.com.au> (raw)
In-Reply-To: <3C69A174.B092D044@zip.com.au>, <3C69A174.B092D044@zip.com.au>; from akpm@zip.com.au on Tue, Feb 12, 2002 at 03:12:52PM -0800 <20020212170313.V9826@lynx.turbolabs.com>
Andreas Dilger wrote:
>
> On Feb 12, 2002 15:12 -0800, Andrew Morton wrote:
> > --- linux-2.4.18-pre9/include/linux/ext2_fs_i.h Mon Sep 17 13:16:30 2001
> > +++ linux-akpm/include/linux/ext2_fs_i.h Tue Feb 12 14:00:11 2002
> > @@ -25,7 +25,6 @@ struct ext2_inode_info {
> > __u32 i_faddr;
> > __u8 i_frag_no;
> > __u8 i_frag_size;
> > - __u16 i_osync;
> > __u32 i_file_acl;
> > __u32 i_dir_acl;
> > __u32 i_dtime;
>
> We should probably leave this in there as a placeholder (with a different
> name), just for alignment sake.
>
hrm. I'd assumed the compiler would get that right.
Otherwise, the __u8's go to the end of the struct.
-
prev parent reply other threads:[~2002-02-13 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 23:12 [patch] ext2 synchronous mount speedup Andrew Morton
2002-02-13 0:03 ` Andreas Dilger
2002-02-13 0:20 ` Andrew Morton [this message]
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=3C69B165.4301DD9A@zip.com.au \
--to=akpm@zip.com.au \
--cc=adilger@turbolabs.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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.