From: "Theodore Ts'o" <tytso@mit.edu>
To: Phillip Susi <phill@thesusis.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Uneccesary flushes waking up suspended disks
Date: Sat, 9 Mar 2024 12:37:00 -0500 [thread overview]
Message-ID: <20240309173700.GB143836@mit.edu> (raw)
In-Reply-To: <87jzmcwijz.fsf@vps.thesusis.net>
On Fri, Mar 08, 2024 at 03:54:40PM -0500, Phillip Susi wrote:
> "Theodore Ts'o" <tytso@mit.edu> writes:
>
> > Another fix would be making sure that the kernel isues the file system
> > syncs, and waits for them to be completed, *before* we freeze the
> > disk. That way, if there are any dirty pages, they can be flushed to
> > stable store so that if the battery runs down while the laptop is
> > suspended, the user won't see data loss.
>
> That's exactly how it works now. The kernel syncs the fs before
> suspending, but during that sync, even though there were no dirty pages
> and so nothing has been written to the disk and it has been runtime
> suspended, the fs issues a flush, which wakes the disk up, only to be
> put right back to sleep so the system can transition to S3.
In an earlier message from you upthread, you had stated "Since the
disk is suspended however, there is nothing in the cache to flush, so
this is wasteful." So that sounded like the flush was happening at
the wrong time, after the disk has already been suspended?
Am I missing something?
Thanks,
- Ted
next prev parent reply other threads:[~2024-03-09 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 13:53 Uneccesary flushes waking up suspended disks Phillip Susi
2024-03-07 15:37 ` Theodore Ts'o
2024-03-08 20:54 ` Phillip Susi
2024-03-09 17:37 ` Theodore Ts'o [this message]
2024-03-12 20:35 ` Phillip Susi
2024-03-11 1:32 ` Dave Chinner
2024-03-15 14:05 ` Phillip Susi
2024-03-16 4:38 ` Darrick J. Wong
2024-03-16 18:35 ` Phillip Susi
2024-03-17 22:45 ` Dave Chinner
2024-03-20 12:38 ` Phillip Susi
2024-03-20 21:58 ` Dave Chinner
2024-03-25 17:09 ` Phillip Susi
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=20240309173700.GB143836@mit.edu \
--to=tytso@mit.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=phill@thesusis.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.