linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 NeilBrown <neilb@suse.de>, Peter Zijlstra <peterz@infradead.org>,
	 Ingo Molnar <mingo@redhat.com>, Jeff Layton <jlayton@kernel.org>,
	Jan Kara <jack@suse.cz>,
	 linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC v2 6/6] inode: make i_state a u32
Date: Thu, 22 Aug 2024 10:31:47 +0200	[thread overview]
Message-ID: <20240822-differenz-reihum-0e9f9e265020@brauner> (raw)
In-Reply-To: <9BA2DBC4-0DB3-406C-A88D-B816C421EF1D@dilger.ca>

On Wed, Aug 21, 2024 at 03:03:01PM GMT, Andreas Dilger wrote:
> On Aug 21, 2024, at 9:47 AM, Christian Brauner <brauner@kernel.org> wrote:
> > 
> > Now that we use the wait var event mechanism make i_state a u32 and free
> > up 4 bytes. This means we currently have two 4 byte holes in struct
> > inode which we can pack.
> > 
> > Signed-off-by: Christian Brauner <brauner@kernel.org>
> > ---
> > include/linux/fs.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > index 8525f8bfd7b9..a673173b6896 100644
> > --- a/include/linux/fs.h
> > +++ b/include/linux/fs.h
> > @@ -681,7 +681,7 @@ struct inode {
> > #endif
> > 
> > 	/* Misc */
> > -	unsigned long		i_state;
> > +	u32			i_state;
> 
> Is it worthwhile to add a comment that there is a hole here, instead
> of leaving it for future re-discovery?
> 
>         /* 32-bit hole */
> 
> > 	struct rw_semaphore	i_rwsem;
> > 
> > 	unsigned long		dirtied_when; /* jiffies of first dirtying */
> 
> Normally this would be excess noise, but since struct inode is
> micro-optimized (like struct page) it probably makes sense to
> document this case.

Good idea. Added now!

  reply	other threads:[~2024-08-22  8:31 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 15:47 [PATCH RFC v2 0/6] inode: turn i_state into u32 Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 1/6] fs: add i_state helpers Christian Brauner
2024-08-21 22:12   ` NeilBrown
2024-08-21 22:47     ` Linus Torvalds
2024-08-21 23:34     ` Dave Chinner
2024-08-23  0:08       ` NeilBrown
2024-08-22  8:27     ` Christian Brauner
2024-08-22  8:37       ` Linus Torvalds
2024-08-23  0:14       ` NeilBrown
2024-08-23  2:52         ` Linus Torvalds
2024-08-23  3:05           ` Linus Torvalds
2024-08-23  3:44             ` Linus Torvalds
2024-08-23  5:01           ` NeilBrown
2024-08-23 12:47           ` [PATCH v3 0/6] inode: turn i_state into u32 Christian Brauner
2024-08-23 12:47             ` [PATCH v3 1/6] fs: add i_state helpers Christian Brauner
2024-09-05 16:01               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 2/6] fs: reorder i_state bits Christian Brauner
2024-09-05 16:02               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 3/6] inode: port __I_SYNC to var event Christian Brauner
2024-09-05 16:02               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 4/6] inode: port __I_NEW " Christian Brauner
2024-09-06 13:30               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 5/6] inode: port __I_LRU_ISOLATING " Christian Brauner
2024-09-09  7:35               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 6/6] inode: make i_state a u32 Christian Brauner
2024-09-09  7:35               ` Jan Kara
2024-08-23 15:06             ` [PATCH v3 0/6] inode: turn i_state into u32 Josef Bacik
2024-08-21 22:28   ` [PATCH RFC v2 1/6] fs: add i_state helpers Dave Chinner
2024-08-21 22:53     ` Linus Torvalds
2024-08-21 15:47 ` [PATCH RFC v2 2/6] fs: reorder i_state bits Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 3/6] writeback: port __I_SYNC to var event Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 4/6] inode: port __I_NEW " Christian Brauner
2024-08-23  0:31   ` NeilBrown
2024-08-23  8:20     ` Christian Brauner
2024-08-23 11:07       ` Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 5/6] inode: port __I_LRU_ISOLATING " Christian Brauner
2024-08-21 19:41   ` Jeff Layton
2024-08-22  8:53     ` Christian Brauner
2024-08-22  9:48       ` Mateusz Guzik
2024-08-22 11:10         ` Christian Brauner
2024-08-22 12:46           ` Mateusz Guzik
2024-08-23  0:36   ` NeilBrown
2024-08-23  2:24     ` Linus Torvalds
2024-08-23  8:29       ` Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 6/6] inode: make i_state a u32 Christian Brauner
2024-08-21 21:03   ` Andreas Dilger
2024-08-22  8:31     ` Christian Brauner [this message]
2024-08-21 19:15 ` [PATCH RFC v2 0/6] inode: turn i_state into u32 Josef Bacik
2024-08-21 19:42 ` Jeff Layton

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=20240822-differenz-reihum-0e9f9e265020@brauner \
    --to=brauner@kernel.org \
    --cc=adilger@dilger.ca \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@suse.de \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).