public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Mike Turquette <mturquette@ti.com>
Cc: "linux-pm@lists.osdl.org" <linux-pm@lists.osdl.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Power management minisummit at Linux Plumbers Conference (November 3-5)
Date: Tue, 3 Aug 2010 21:34:31 +0100	[thread overview]
Message-ID: <20100803203431.GA2969@srcf.ucam.org> (raw)
In-Reply-To: <4C587C80.3040207@ti.com>

On Tue, Aug 03, 2010 at 03:30:56PM -0500, Mike Turquette wrote:

> That link did not really work for me, but I think I found the right  
> place after a few clicks.

Oops! The link should have been 
http://www.linuxplumbersconf.org/2010/ocw/events/LPC2010MC/proposals .

> Just FYI, I proposed a discussion on the issues that create such a large  
> power gap between a CPUIdle-only system and a system with suspend (with  
> the assumption that the lowest C-state can be hit by both).
>
> I don't really want to present a formal lecture on it, but it would be  
> nice to discuss with the group what can be done to shrink that gap a  
> little in kernel space (badly behaving timers in platform-independent  
> code) and in userspace (power-aware timers, coalescing timers, etc).

That sounds great. The idea is to be fairly discussion-oriented, perhaps 
with a short presentation to cover the outline of the issue, so this 
kind of topic is ideal.

Thanks,
-- 
Matthew Garrett | mjg59@srcf.ucam.org

      reply	other threads:[~2010-08-03 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 18:27 Power management minisummit at Linux Plumbers Conference (November 3-5) Matthew Garrett
2010-08-03 20:30 ` [linux-pm] " Mike Turquette
2010-08-03 20:34   ` Matthew Garrett [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=20100803203431.GA2969@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mturquette@ti.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