From: "Theodore Tso" <tytso@mit.edu>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: bcrl@kvack.org, viro@zeniv.linux.org.uk, brauner@kernel.org,
jack@suse.cz, adilger.kernel@dilger.ca,
libaokun@linux.alibaba.com, ojaswin@linux.ibm.com,
ritesh.list@gmail.com, yi.zhang@huawei.com, sforshee@kernel.org,
akpm@linux-foundation.org, pmladek@suse.com, rostedt@goodmis.org,
andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
senozhatsky@chromium.org, kees@kernel.org, tglx@kernel.org,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v3 0/8] Convert barrier pairs to acquire/release for better performance
Date: Wed, 2 Sep 2026 10:19:46 -0400 [thread overview]
Message-ID: <apgv5w116frzutwH@mit.edu> (raw)
In-Reply-To: <20260902074805.398540-1-ruanjinjie@huawei.com>
On Wed, Sep 02, 2026 at 03:47:57PM -0500, Jinjie Ruan wrote:
>
> This series converts some existing smp_wmb()/smp_rmb() barrier pairs to
> smp_store_release()/smp_load_acquire() across various subsystems.
I would like to land the ext4 related patches through the ext4 tree,
so please detach them from this patch series. That's because I want
to be able to monitor the regression testing before sending a pull
request to Linus.
More generally, I think we should be looking at this kind of barrier
conversion on a per site basis. If there is a bug that isn't notice,
it can result in a very hard to debug problem. And if the benefit of
speeding up a particular code path isn't particularly that great,
maybe the cost vs benefit vs risk calculation might cause us to decide
to take a pass on the change.
Cheers,
- Ted
next prev parent reply other threads:[~2026-09-02 14:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 7:47 [PATCH v3 0/8] Convert barrier pairs to acquire/release for better performance Jinjie Ruan
2026-09-02 7:47 ` [PATCH v3 1/8] user_namespace: Use acquire/release for nr_extents synchronization Jinjie Ruan
2026-09-02 10:09 ` Bradley Morgan
2026-09-02 13:03 ` Andy Shevchenko
2026-09-02 13:04 ` Andy Shevchenko
2026-09-03 1:42 ` Jinjie Ruan
2026-09-03 2:16 ` Jinjie Ruan
2026-09-02 7:47 ` [PATCH v3 2/8] lib/vsprintf: Use acquire/release for ptr_key publication Jinjie Ruan
2026-09-04 13:13 ` Petr Mladek
2026-09-02 7:48 ` [PATCH v3 3/8] fs: aio: Use acquire/release for ring->tail publication Jinjie Ruan
2026-09-02 7:48 ` [PATCH v3 4/8] fs: Use acquire/release for fdtable resize synchronization Jinjie Ruan
2026-09-02 7:48 ` [PATCH v3 5/8] pidfs: Use test_bit_acquire() for attr flag tests Jinjie Ruan
2026-09-02 7:48 ` [PATCH v3 6/8] super: Use acquire for SB_BORN check in super_cache_count() Jinjie Ruan
2026-09-02 7:48 ` [PATCH v3 7/8] ext4: Fix out-of-bounds read in ext4_get_group_info() Jinjie Ruan
2026-09-02 7:48 ` [PATCH v3 8/8] ext4: Convert group-count barrier protocol to acquire/release Jinjie Ruan
2026-09-02 14:19 ` Theodore Tso [this message]
2026-09-02 14:56 ` [PATCH v3 0/8] Convert barrier pairs to acquire/release for better performance Jan Kara
2026-09-04 7:20 ` Jinjie Ruan
2026-09-04 12:28 ` Petr Mladek
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=apgv5w116frzutwH@mit.edu \
--to=tytso@mit.edu \
--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=jack@suse.cz \
--cc=kees@kernel.org \
--cc=libaokun@linux.alibaba.com \
--cc=linux-aio@kvack.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ojaswin@linux.ibm.com \
--cc=pmladek@suse.com \
--cc=ritesh.list@gmail.com \
--cc=rostedt@goodmis.org \
--cc=ruanjinjie@huawei.com \
--cc=senozhatsky@chromium.org \
--cc=sforshee@kernel.org \
--cc=tglx@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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