From: Nigel Cunningham <ncunningham@crca.org.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org, "Leisner,
Martin" <Martin.Leisner@xerox.com>
Subject: Re: syncing the disks when entering sleep
Date: Sat, 23 Jan 2010 08:31:46 +1100 [thread overview]
Message-ID: <4B5A1942.2050003@crca.org.au> (raw)
In-Reply-To: <201001222149.46839.rjw@sisk.pl>
Hi.
Rafael J. Wysocki wrote:
> On Friday 22 January 2010, Leisner, Martin wrote:
>> I noticed when we enter sleep states, it seems there's always a
>> sys_sync given.
>>
>> When having an embedded system doing WOL (already in laptop mode to
>> cache
>> all the writes), it reasonable to wake up dozens of times of day and
>> quickly go back to sleep. If the disk is not spun up,
>> and there's some work to be done, won't the sys_sync spin up the disk
>> before going to sleep?
>>
>> It would be good to have a knob (in /sys) you can tweak from usespace to
>>
>> configure the behavior of whether you want to do a sync when entering
>> sleep.
>>
>> The ideal behavior would be:
>>
>> if(disk is spun up)
>> then let the sync happen
>
> I'm not against that. Patch welcome. :-)
Oooh. I am. That's providing potential for unpredictable behaviour. Much
better IMO would be providing a tuning know that explicitly and
unconditionally disables syncing.
Regards,
Nigel
next prev parent reply other threads:[~2010-01-22 21:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 15:59 syncing the disks when entering sleep Leisner, Martin
2010-01-22 20:49 ` Rafael J. Wysocki
2010-01-22 21:31 ` Nigel Cunningham [this message]
2010-01-22 21:33 ` Leisner, Martin
2010-01-22 21:38 ` Rafael J. Wysocki
2010-01-22 21:40 ` Leisner, Martin
2010-01-22 21:55 ` Nigel Cunningham
2010-01-22 22:06 ` Nigel Cunningham
2010-01-22 21:35 ` Rafael J. Wysocki
2010-01-26 13:59 ` Pavel Machek
2010-01-26 18:17 ` Rafael J. Wysocki
2010-01-26 14:51 ` Pavel Machek
2010-01-27 0:51 ` Rafael J. Wysocki
2010-01-27 6:45 ` Pavel Machek
2010-01-27 7:29 ` Nigel Cunningham
2010-01-27 20:50 ` Rafael J. Wysocki
2010-01-28 7:26 ` Pavel Machek
2010-01-28 10:43 ` Rafael J. Wysocki
2010-04-05 6:38 ` document open(/dev/snapshot) sideeffects -- was Re: [linux-pm] " Pavel Machek
2010-04-23 18:28 ` Rafael J. Wysocki
2010-04-24 5:42 ` Pavel Machek
2010-04-24 5:42 ` document open(/dev/snapshot) sideeffects -- was " Pavel Machek
2010-04-23 18:28 ` Rafael J. Wysocki
2010-04-05 6:38 ` Pavel Machek
2010-01-27 9:55 ` Pavel Machek
2010-01-27 20:46 ` Rafael J. Wysocki
2010-01-31 8:52 ` Pavel Machek
2010-01-31 12:33 ` Rafael J. Wysocki
2010-02-01 10:49 ` Pavel Machek
2010-02-01 17:13 ` Leisner, Martin
2010-02-01 21:09 ` Pavel Machek
2010-02-02 4:13 ` Nigel Cunningham
2010-02-10 8:13 ` Pavel Machek
2010-02-10 10:34 ` Rafael J. Wysocki
2010-02-10 10:38 ` Oliver Neukum
2010-02-10 10:58 ` Rafael J. Wysocki
2010-02-10 11:02 ` Oliver Neukum
2010-02-10 18:42 ` Rafael J. Wysocki
2010-02-15 20:28 ` Matthew Garrett
2010-02-16 6:38 ` Pavel Machek
2010-02-10 13:31 ` Pavel Machek
2010-02-10 19:19 ` Rafael J. Wysocki
2010-02-10 21:17 ` Leisner, Martin
2010-02-11 14:49 ` Pavel Machek
2010-02-11 15:00 ` Pavel Machek
2010-02-11 17:28 ` Rafael J. Wysocki
2010-02-11 20:17 ` Nigel Cunningham
2010-02-10 20:58 ` Leisner, Martin
2010-02-01 20:55 ` Nigel Cunningham
2010-02-01 21:07 ` Pavel Machek
2010-02-01 22:03 ` Nigel Cunningham
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=4B5A1942.2050003@crca.org.au \
--to=ncunningham@crca.org.au \
--cc=Martin.Leisner@xerox.com \
--cc=linux-pm@lists.linux-foundation.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.