From: Pavel Machek <pavel@ucw.cz>
To: Len Brown <lenb@kernel.org>
Cc: rjw@sisk.pl, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 1/1] suspend: make sync() on suspend-to-RAM optional
Date: Sun, 26 Jan 2014 22:08:50 +0100 [thread overview]
Message-ID: <20140126210850.GA7246@Nokia-N900> (raw)
In-Reply-To: <ce1b9fc9cdcfd1fe8f9f3b8570421271dc15ae75.1390460951.git.len.brown@intel.com>
Hi!
> From: Len Brown <len.brown@intel.com>
>
> Linux suspend-to-RAM was unreliable when first developed,
> and so sys_sync() was invoked inside the kernel at the
> start of every suspend flow.
>
> Today, many devices are invoking suspend with
> high reliability and high frequency, and they don't
> want to be forced to pay for sync on every suspend.
>
> So here we make it optional.
> De-select CONFIG_PM_SLEEP_SYNC to delete the call entirely.
> or keep CONFIG_PM_SLEEP and you can now clear the
> sys/power/sleep_sync attribte to disable the sync
> from user-space.
Dunno. Config option plus sysfs attribute is overdoing it a bit.
Maybe we could do
echo memfast > state
to enter suspend without sync? Patch should be simpler that way,
and we won't have to keep the state...
Pavel
next prev parent reply other threads:[~2014-01-26 21:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 7:11 [PATCH 1/1] suspend: make sync() on suspend-to-RAM optional Len Brown
2014-01-23 7:29 ` Zhang Rui
2014-01-23 7:41 ` Brown, Len
2014-01-23 7:41 ` Brown, Len
2014-01-23 7:38 ` Srivatsa S. Bhat
2014-01-23 7:59 ` Brown, Len
2014-01-26 21:08 ` Pavel Machek [this message]
2015-05-08 6:41 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2015-07-15 2:24 [PATCH v4 0/1] " Len Brown
2015-07-15 2:24 ` [PATCH 1/1] " Len Brown
2015-07-15 6:43 ` Pavel Machek
2015-07-15 14:06 ` Austin S Hemmelgarn
2015-07-15 14:58 ` Brown, Len
2015-07-17 23:54 ` Rafael J. Wysocki
2015-07-21 9:38 ` Pavel Machek
2015-07-21 14:41 ` Rafael J. Wysocki
2015-07-21 15:19 ` Pavel Machek
2015-07-21 15:36 ` Austin S Hemmelgarn
2015-07-21 20:11 ` Pavel Machek
2015-07-21 20:01 ` Brown, Len
2015-07-21 20:05 ` Pavel Machek
2015-07-22 1:25 ` Rafael J. Wysocki
2015-07-22 7:23 ` Pavel Machek
2015-07-22 8:55 ` Oliver Neukum
2015-07-31 16:02 ` Len Brown
2015-07-31 23:56 ` Rafael J. Wysocki
2015-10-08 15:50 ` Pavel Machek
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=20140126210850.GA7246@Nokia-N900 \
--to=pavel@ucw.cz \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.