Netdev List
 help / color / mirror / Atom feed
From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Jan Kara <jack@suse.cz>
Cc: <viro@zeniv.linux.org.uk>, <brauner@kernel.org>, <bcrl@kvack.org>,
	<tytso@mit.edu>, <adilger.kernel@dilger.ca>,
	<libaokun@linux.alibaba.com>, <ojaswin@linux.ibm.com>,
	<ritesh.list@gmail.com>, <yi.zhang@huawei.com>,
	<pmladek@suse.com>, <rostedt@goodmis.org>,
	<andriy.shevchenko@linux.intel.com>, <linux@rasmusvillemoes.dk>,
	<senozhatsky@chromium.org>, <akpm@linux-foundation.org>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <horms@kernel.org>, <socketcan@hartkopp.net>,
	<mkl@pengutronix.de>, <kuniyu@google.com>, <willemb@google.com>,
	<jhs@mojatatu.com>, <jiri@resnulli.us>, <kees@kernel.org>,
	<cyphar@cyphar.com>, <tglx@kernel.org>, <liuhangbin@gmail.com>,
	<sdf@fomichev.me>, <nb@tipi-net.de>,
	<linux-fsdevel@vger.kernel.org>, <linux-aio@kvack.org>,
	<linux-kernel@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
	<netdev@vger.kernel.org>, <linux-can@vger.kernel.org>
Subject: Re: [PATCH 06/11] super: Use acquire for SB_BORN check in super_cache_count()
Date: Mon, 31 Aug 2026 20:46:01 +0800	[thread overview]
Message-ID: <0e26fbf2-3dfe-4c73-819e-8255289f7610@huawei.com> (raw)
In-Reply-To: <2uxxlu75vyo7iayzz2udisjmu7dhyiyboiuodriksmorz37cha@3mzh2vwrmafw>



在 2026/8/31 20:29, Jan Kara 写道:
> On Tue 25-08-26 17:54:17, Jinjie Ruan wrote:
>> The active SB_BORN check in super_cache_count() pairs with the
>> smp_store_release() in super_wake() when publishing a newly initialized
>> superblock.
>>
>> Replace the historical independent smp_rmb() barrier with an acquire load
>> on sb->s_flags. This expresses the publish-subscribe pattern more clearly
>> and allows weakly-ordered architectures like arm64 to utilize efficient
>> native instructions (e.g., LDAR) instead of a full one-way barrier.
>>
>> Also update the outdated comment to correctly point to super_wake().
>>
>> Assisted-by: Gemini:Gemini-3.1
>> Assisted-by: DeepSeek:DeepSeek-V3
>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> 
> Looks good. Just one nit below. With that addressed feel free to add:
> 
> Reviewed-by: Jan Kara <jack@suse.cz>
> 
>> diff --git a/fs/super.c b/fs/super.c
>> index 05e443173038..5860daea6d40 100644
>> --- a/fs/super.c
>> +++ b/fs/super.c
>> @@ -267,12 +267,11 @@ static unsigned long super_cache_count(struct shrinker *shrink,
>>  	 * However, if we are currently mounting the superblock, the underlying
>>  	 * filesystem might be in a state of partial construction and hence it
>>  	 * is dangerous to access it.  super_trylock_shared() uses a SB_BORN check
>> -	 * to avoid this situation, so do the same here. The memory barrier is
>> -	 * matched with the one in mount_fs() as we don't hold locks here.
>> +	 * to avoid this situation, so do the same here. The acquire is matched
>> +	 * with the smp_store_release() in super_wake() as we don't hold locks here.
>>  	 */
>> -	if (!(sb->s_flags & SB_BORN))
>> +	if (!(smp_load_acquire(&sb->s_flags) & SB_BORN))
>>  		return 0;
> 
> We have super_flags() helper exactly for checks like this so it would be
> good to use it here.

Right! And we can just remove the outdated memory barrier comment, as
the underlying super_flags() implementation already has a self-document.

> 
> 								Honza
> 
>> -	smp_rmb();
>>  
>>  	if (sb->s_op && sb->s_op->nr_cached_objects &&
>>  	    super_fs_objects_eligible(sc))
>> -- 
>> 2.34.1
>>


  reply	other threads:[~2026-08-31 12:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  9:54 [PATCH 00/11] Convert barrier pairs to acquire/release for better performance Jinjie Ruan
2026-08-25  9:54 ` [PATCH 01/11] user_namespace: Use acquire/release for nr_extents synchronization Jinjie Ruan
2026-08-25  9:54 ` [PATCH 02/11] lib/vsprintf: Use acquire/release for ptr_key publication Jinjie Ruan
2026-08-25  9:54 ` [PATCH 03/11] fs: aio: Use acquire/release for ring->tail publication Jinjie Ruan
2026-08-31 12:13   ` Jan Kara
2026-09-01  1:44     ` Jinjie Ruan
2026-08-25  9:54 ` [PATCH 04/11] fs: Use acquire/release for fdtable resize synchronization Jinjie Ruan
2026-08-31 12:22   ` Jan Kara
2026-08-25  9:54 ` [PATCH 05/11] pidfs: Use test_bit_acquire() for attr flag tests Jinjie Ruan
2026-08-25  9:54 ` [PATCH 06/11] super: Use acquire for SB_BORN check in super_cache_count() Jinjie Ruan
2026-08-31 12:29   ` Jan Kara
2026-08-31 12:46     ` Jinjie Ruan [this message]
2026-08-25  9:54 ` [PATCH 07/11] ext4: Convert group-count barrier protocol to acquire/release Jinjie Ruan
2026-08-31 11:53   ` Jan Kara
2026-08-31 12:18   ` Zhang Yi
2026-08-25  9:54 ` [PATCH 08/11] soreuseport: publish num_socks with acquire/release Jinjie Ruan
2026-08-25  9:54 ` [PATCH 09/11] net: sched: act_gact: use acquire/release for tcfg_ptype Jinjie Ruan
2026-08-25  9:54 ` [PATCH 10/11] 8021q: publish vlan_devices_arrays entries with acquire/release Jinjie Ruan
2026-08-25  9:54 ` [PATCH 11/11] can: isotp: publish tx.state with smp_store_release() Jinjie Ruan
2026-08-25 11:46   ` Oliver Hartkopp
2026-08-26  3:33     ` Jinjie Ruan
2026-08-26  8:04       ` Oliver Hartkopp

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=0e26fbf2-3dfe-4c73-819e-8255289f7610@huawei.com \
    --to=ruanjinjie@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bcrl@kvack.org \
    --cc=brauner@kernel.org \
    --cc=cyphar@cyphar.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jack@suse.cz \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=liuhangbin@gmail.com \
    --cc=mkl@pengutronix.de \
    --cc=nb@tipi-net.de \
    --cc=netdev@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=pabeni@redhat.com \
    --cc=pmladek@suse.com \
    --cc=ritesh.list@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=sdf@fomichev.me \
    --cc=senozhatsky@chromium.org \
    --cc=socketcan@hartkopp.net \
    --cc=tglx@kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willemb@google.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