All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@ti.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
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, 03 Aug 2010 15:30:56 -0500	[thread overview]
Message-ID: <4C587C80.3040207@ti.com> (raw)
In-Reply-To: <20100803182746.GA32276@srcf.ucam.org>

Matthew Garrett wrote:
> I'm planning on finalising the schedule for the power management 
> minisummit at the Linux Plumbers Conference by the end of this week. If 
> anyone has topics that they'd like to discuss (or be discussed, if you 
> can't make it) then please let me know or register at 
> http://www.linuxplumbersconf.org/2010/ocw/events/proposals/ and file a 

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

> proposal there. We're likely to be concentrating on userspace/kernel 
> interaction rather than pure kernel topics, so if you've got anything to 
> say about how we can handle application requirements without 
> compromising on our power savings then we'd love to hear from you.

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).

This is not intended to be another suspend-blocker discussion, but more 
of a discussion on what it takes to get CPUIdle to be more effective.

Regards,
Mike

  reply	other threads:[~2010-08-03 20:31 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 ` Mike Turquette [this message]
2010-08-03 20:34   ` [linux-pm] " Matthew Garrett

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=4C587C80.3040207@ti.com \
    --to=mturquette@ti.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mjg59@srcf.ucam.org \
    /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.