From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Baokun Li <libaokun@linux.alibaba.com>, Jan Kara <jack@suse.cz>,
Christian Brauner <brauner@kernel.org>, Tejun Heo <tj@kernel.org>,
linux-fsdevel@vger.kernel.org,
Eric Hagberg <ehagberg@janestreet.com>
Subject: Re: [PATCH 6.18.y] writeback: use a per-sb counter to drain inode wb switches at umount
Date: Fri, 20 Nov 2026 15:38:55 -0500 [thread overview]
Message-ID: <2026-11-20-1-daily-reply-0006@kernel.org> (raw)
In-Reply-To: <20261119185222.1147448-1-ehagberg@janestreet.com>
> Replace the global synchronize_rcu()/flush_workqueue() pair with a
> per-sb counter, s_isw_nr_in_flight, plus three small helpers:
Queued for 6.18, thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-20 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 18:52 [PATCH 6.18.y] writeback: use a per-sb counter to drain inode wb switches at umount Eric Hagberg
2026-11-20 20:38 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-19 18:51 Eric Hagberg
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=2026-11-20-1-daily-reply-0006@kernel.org \
--to=sashal@kernel.org \
--cc=brauner@kernel.org \
--cc=ehagberg@janestreet.com \
--cc=jack@suse.cz \
--cc=libaokun@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.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