From: Oliver Neukum <oneukum@suse.com>
To: tuhaowen <tuhaowen@uniontech.com>, pavel@kernel.org, rafael@kernel.org
Cc: saravanak@google.com, huangbibo@uniontech.com,
len.brown@intel.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, wusamuel@google.com
Subject: Re: Different approaches to sync timeout: Desktop vs Mobile use cases
Date: Tue, 9 Sep 2025 10:51:21 +0200 [thread overview]
Message-ID: <30807256-d5f4-4550-8e1d-aedee05dc667@suse.com> (raw)
In-Reply-To: <20250909071358.5943-1-tuhaowen@uniontech.com>
Hi,
On 09.09.25 09:13, tuhaowen wrote:
> **Use Case**: Desktop/laptop systems where users expect immediate feedback
> **Problem**: When large file operations are in progress (e.g., copying
> files to USB drives) and users initiate suspend, ksys_sync() can hang
It seems to me like both your approaches seek to mitigate
the consequences of the issue rather than solve it.
Your issue is that you have too many dirty blocks associated
with a slow device.
In other words, you should sync and need to limit the number
of dirty blocks created after you've started syncing without
freezing all of user space.
Regards
Oliver
prev parent reply other threads:[~2025-09-09 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 2:46 Sync timeout mechanisms - Request for coordination tuhaowen
2025-09-09 2:00 ` Saravana Kannan
2025-09-09 2:45 ` [PATCH v2] PM: Add configurable sync timeout for suspend and hibernation tuhaowen
2025-09-09 6:18 ` Saravana Kannan
2025-09-09 7:13 ` Different approaches to sync timeout: Desktop vs Mobile use cases tuhaowen
2025-09-09 8:51 ` Oliver Neukum [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=30807256-d5f4-4550-8e1d-aedee05dc667@suse.com \
--to=oneukum@suse.com \
--cc=huangbibo@uniontech.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=tuhaowen@uniontech.com \
--cc=wusamuel@google.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