From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934054Ab0EZKkJ (ORCPT ); Wed, 26 May 2010 06:40:09 -0400 Received: from smtp-out.google.com ([74.125.121.35]:18170 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750727Ab0EZKkG convert rfc822-to-8bit (ORCPT ); Wed, 26 May 2010 06:40:06 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=iGeIU0L0J9L2rMfktiMI/4lkkrEbN0t8tEU3GHZGJP5AllpsfwssCW5WHBcbujbgi qE9fXMWixchNmmsIYh9cw== MIME-Version: 1.0 In-Reply-To: <1274869966.5882.5262.camel@twins> References: <1274482015-30899-1-git-send-email-arve@android.com> <201005242049.18920.rjw@sisk.pl> <87wrusvrqe.fsf@deeprootsystems.com> <201005250138.16293.rjw@sisk.pl> <1274863655.5882.4875.camel@twins> <1274867106.5882.5090.camel@twins> <1274868593.5882.5185.camel@twins> <1274869966.5882.5262.camel@twins> Date: Wed, 26 May 2010 03:40:01 -0700 Message-ID: Subject: Re: [PATCH 0/8] Suspend block api (version 8) From: Brian Swetland To: Peter Zijlstra Cc: =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , "Rafael J. Wysocki" , Kevin Hilman , felipe.balbi@nokia.com, Linux PM , LKML , Linux OMAP Mailing List , Tony Lindgren , Paul Walmsley Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 26, 2010 at 3:32 AM, Peter Zijlstra wrote: > On Wed, 2010-05-26 at 03:25 -0700, Arve Hjønnevåg wrote: > >> and on systems where the >> same power state can be used from idle and suspend, we use suspend so >> we can stay in the low power state for minutes to hours instead of >> milliseconds to seconds. > > So don't you think working on making it possible for systems to be idle > _that_ long would improve things for everybody? as opposed to this > auto-suspend which only improves matters for those that (can) use it? As we've stated a number of times in the several weeks of discussion (this time around) of this patchset, we are all in favor of improving runtime pm, finding and resolving issues that prevent idle, and heading toward ever lower power states in idle -- after all, this benefits our battery life in the cases when the system is not suspended as well as moving us closer to a future where the power savings between actively entering suspend and not doing so approach zero. Aggressively entering the lowest possible power state at all times is our goal here. At the moment, the power savings from opportunistic suspend do directly lead to improved battery life, and there are some advantages to this model in the face of a non-optimal userspace (as we encounter in a world where there are not restrictions on what applications users may install and run). Brian