From: Jan Kara <jack@suse.cz>
To: libaokun@huaweicloud.com
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, jack@suse.cz,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH 5/5] ext4: pack holes in ext4_inode_info
Date: Fri, 20 Dec 2024 12:06:20 +0100 [thread overview]
Message-ID: <20241220110620.keisbqz7a7tkn7zz@quack3> (raw)
In-Reply-To: <20241220060757.1781418-6-libaokun@huaweicloud.com>
On Fri 20-12-24 14:07:57, libaokun@huaweicloud.com wrote:
> From: Baokun Li <libaokun1@huawei.com>
>
> When CONFIG_DEBUG_SPINLOCK is not enabled (general case), there are four
> 4 bytes holes and one 2 bytes hole in struct ext4_inode_info. Move the
> members to pack the four 4 bytes holes.
>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext4/ext4.h | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 203a900fd789..345dda2310d0 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -1060,6 +1060,8 @@ struct ext4_inode_info {
> /* Number of ongoing updates on this inode */
> atomic_t i_fc_updates;
>
> + spinlock_t i_raw_lock; /* protects updates to the raw inode */
> +
> /* Fast commit wait queue for this inode */
> wait_queue_head_t i_fc_wait;
>
> @@ -1097,8 +1099,6 @@ struct ext4_inode_info {
> struct inode vfs_inode;
> struct jbd2_inode *jinode;
>
> - spinlock_t i_raw_lock; /* protects updates to the raw inode */
> -
> /*
> * File creation time. Its function is same as that of
> * struct timespec64 i_{a,c,m}time in the generic inode.
> @@ -1141,6 +1141,7 @@ struct ext4_inode_info {
> /* quota space reservation, managed internally by quota code */
> qsize_t i_reserved_quota;
> #endif
> + spinlock_t i_block_reservation_lock;
>
> /* Lock protecting lists below */
> spinlock_t i_completed_io_lock;
> @@ -1151,8 +1152,6 @@ struct ext4_inode_info {
> struct list_head i_rsv_conversion_list;
> struct work_struct i_rsv_conversion_work;
>
> - spinlock_t i_block_reservation_lock;
> -
> /*
> * Transactions that contain inode's metadata needed to complete
> * fsync and fdatasync, respectively.
> --
> 2.46.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-12-20 11:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 6:07 [PATCH 0/5] ext4: fix issues caused by data write-back failures libaokun
2024-12-20 6:07 ` [PATCH 1/5] ext4: replace opencoded ext4_end_io_end() in ext4_put_io_end() libaokun
2024-12-20 10:22 ` Markus Elfring
2024-12-20 10:26 ` Jan Kara
2024-12-20 6:07 ` [PATCH 2/5] ext4: do not convert the unwritten extents if data writeback fails libaokun
2024-12-20 10:28 ` Jan Kara
2024-12-20 6:07 ` [PATCH 3/5] ext4: abort journal on data writeback failure if in data_err=abort mode libaokun
2024-12-20 10:36 ` Jan Kara
2024-12-20 13:39 ` Baokun Li
2025-01-06 14:32 ` Jan Kara
2025-01-08 3:43 ` Baokun Li
2025-01-08 13:43 ` Jan Kara
2025-01-08 14:44 ` Baokun Li
2025-01-08 15:28 ` Jan Kara
2025-01-09 2:45 ` Baokun Li
2024-12-20 6:07 ` [PATCH 4/5] ext4: remove unused member 'i_unwritten' from 'ext4_inode_info' libaokun
2024-12-20 11:05 ` Jan Kara
2024-12-20 6:07 ` [PATCH 5/5] ext4: pack holes in ext4_inode_info libaokun
2024-12-20 11:06 ` Jan Kara [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=20241220110620.keisbqz7a7tkn7zz@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=libaokun1@huawei.com \
--cc=libaokun@huaweicloud.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.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