[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJvTdKk7tHoDC7N3=_7JB3KFSVrKyAhEEoS+RaM3bud=H4XXuw@mail.gmail.com>
Date: Mon, 11 May 2015 16:22:26 -0400
From: Len Brown <lenb@...nel.org>
To: Dave Chinner <david@...morbit.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux PM list <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 1/1] suspend: delete sys_sync()
On Sun, May 10, 2015 at 9:44 PM, Dave Chinner <david@...morbit.com> wrote:
> ...Please explain what your use case is that makes this
> so prohibitively expensive it needs to be removed.
wake on packet, process packet without turning on the display,
immediately suspend. Do this potentially several times per second.
>> The user-space utilities s2ram and s2disk choose to invoke sync() today.
>> A user can invoke suspend directly via /sys/power/state to skip that cost.
>
> So, you want to have s2disk write all the dirty pages in memory to
> the suspend image, rather than to the filesystem?
The s2disk utility is unchanged by this proposal, it already includes a sync().
cheers,
Len Brown, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists