From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jan Kara <jack@suse.cz>
Cc: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org,
lsf-pc@lists.linux-foundation.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@kernel.org>, Len Brown <len.brown@intel.com>,
linux-pm@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Filesystem Suspend Resume
Date: Thu, 27 Mar 2025 10:28:35 -0400 [thread overview]
Message-ID: <25f2c7dd471077d816ad29e461c6d762921927e1.camel@HansenPartnership.com> (raw)
In-Reply-To: <45d6ff00d8068ee87ccc396ae28c7931b8c3306c.camel@HansenPartnership.com>
On Wed, 2025-03-26 at 11:25 -0400, James Bottomley wrote:
> On Wed, 2025-03-26 at 15:59 +0100, Jan Kara wrote:
> [...]
> > So to summarize I think we may need to introduce freezable variant
> > of
> > percpu_rwsem_down_read() and use it in sb_start_write().
>
> Aye, aye, sir! and thanks for making the can of worms bigger ...
>
> This is what I came up with for freezable variants of the
> sb_write_start(). I'm still building the kernel (laptop only ...) so
> I'll let you know in an hour or so if it actually works.
Slightly longer than an hour, but I can confirm this all works. I've
also tested it with filesystem on loop on filesystem (with ext4 as
upper and lower) and it hibernates just fine running some fio stress.
I've posted what I'm currently working with here:
https://lore.kernel.org/all/20250327140613.25178-1-James.Bottomley@HansenPartnership.com/
So people can see what I'm currently playing with.
Regards,
James
prev parent reply other threads:[~2025-03-27 14:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0a76e074ef262ca857c61175dd3d0dc06b67ec42.camel@HansenPartnership.com>
[not found] ` <Z9xG2l8lm7ha3Pf2@infradead.org>
[not found] ` <acae7a99f8acb0ebf408bb6fc82ab53fb687559c.camel@HansenPartnership.com>
2025-03-21 5:23 ` [LSF/MM/BPF TOPIC] Filesystem Suspend Resume Christoph Hellwig
2025-03-21 12:34 ` James Bottomley
2025-03-21 17:00 ` James Bottomley
2025-03-21 17:17 ` Lukas Wunner
2025-03-21 18:20 ` James Bottomley
2025-03-24 11:38 ` [Lsf-pc] " Jan Kara
2025-03-24 14:34 ` James Bottomley
2025-03-24 19:28 ` Jan Kara
2025-03-27 14:55 ` Eric Sandeen
2025-03-27 17:30 ` Jan Kara
2025-03-24 20:56 ` Dave Chinner
2025-03-24 20:50 ` Dave Chinner
2025-03-24 21:02 ` James Bottomley
2025-03-24 21:07 ` Dave Chinner
2025-03-25 13:42 ` Jan Kara
2025-03-26 2:36 ` James Bottomley
2025-03-26 14:59 ` Jan Kara
2025-03-26 15:25 ` James Bottomley
2025-03-27 14:28 ` James Bottomley [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=25f2c7dd471077d816ad29e461c6d762921927e1.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=len.brown@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=pavel@kernel.org \
--cc=rafael@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