From: "Darrick J. Wong" <djwong@kernel.org>
To: Junchao Sun <sunjunchao2870@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
chandan.babu@oracle.com
Subject: Re: [PATCH 1/2] xfs: reorder xfs_inode structure elements to remove unneeded padding.
Date: Tue, 18 Jun 2024 09:23:27 -0700 [thread overview]
Message-ID: <20240618162327.GE103034@frogsfrogsfrogs> (raw)
In-Reply-To: <20240618113505.476072-1-sunjunchao2870@gmail.com>
On Tue, Jun 18, 2024 at 07:35:04PM +0800, Junchao Sun wrote:
> By reordering the elements in the xfs_inode structure, we can
> reduce the padding needed on an x86_64 system by 8 bytes.
Does this result in denser packing of xfs_inode objects in the slab
page?
--D
> Signed-off-by: Junchao Sun <sunjunchao2870@gmail.com>
> ---
> fs/xfs/xfs_inode.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_inode.h b/fs/xfs/xfs_inode.h
> index 292b90b5f2ac..3239ae4e33d2 100644
> --- a/fs/xfs/xfs_inode.h
> +++ b/fs/xfs/xfs_inode.h
> @@ -40,8 +40,8 @@ typedef struct xfs_inode {
> /* Transaction and locking information. */
> struct xfs_inode_log_item *i_itemp; /* logging information */
> struct rw_semaphore i_lock; /* inode lock */
> - atomic_t i_pincount; /* inode pin count */
> struct llist_node i_gclist; /* deferred inactivation list */
> + atomic_t i_pincount; /* inode pin count */
>
> /*
> * Bitsets of inode metadata that have been checked and/or are sick.
> --
> 2.39.2
>
>
next prev parent reply other threads:[~2024-06-18 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 11:35 [PATCH 1/2] xfs: reorder xfs_inode structure elements to remove unneeded padding Junchao Sun
2024-06-18 11:35 ` [PATCH 2/2] vfs: reorder struct file " Junchao Sun
2024-06-18 14:52 ` Christian Brauner
2024-06-18 16:23 ` Darrick J. Wong [this message]
2024-06-18 16:40 ` [PATCH 1/2] xfs: reorder xfs_inode " JunChao Sun
2024-06-18 16:51 ` Matthew Wilcox
2024-06-19 10:05 ` JunChao Sun
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=20240618162327.GE103034@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sunjunchao2870@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).