public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Dave Jones <davej@redhat.com>, Con Kolivas <kernel@kolivas.org>,
	ck list <ck@vds.kolivas.org>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-ck1
Date: Thu, 12 Jan 2006 19:42:36 -0500	[thread overview]
Message-ID: <20060113004236.GB11601@neo.rr.com> (raw)
In-Reply-To: <20060112230315.GO19827@redhat.com>

On Thu, Jan 12, 2006 at 06:03:15PM -0500, Dave Jones wrote:
> On Thu, Jan 12, 2006 at 05:11:33PM -0500, Adam Belay wrote:
>  > It might be possible to do even a little better.  Currently, I'm developing a
>  > new ACPI idle policy that tries to take advantage of the long time we may
>  > be able to spend in a C3 state.
> 
> As soon as that usb timer hits (every 250ms iirc) you'll bounce back out
> of any low-power state you may be in. It's a bit craptastic that we do
> this, even if we don't have any USB devices plugged in.
> 
> 		Dave

I agree that's annoying, but isn't 250ms not often enough to make any
significant difference as far as power management is concerned?
Generally some bus master activity will come along in a shorter time frame,
causing a jump out of C3.

Thanks,
Adam

  reply	other threads:[~2006-01-13  0:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  1:00 2.6.15-ck1 Con Kolivas
2006-01-04 19:05 ` 2.6.15-ck1 Dave Jones
2006-01-04 19:57   ` 2.6.15-ck1 Dave Jones
2006-01-04 20:33     ` 2.6.15-ck1 Arjan van de Ven
2006-01-04 21:22       ` 2.6.15-ck1 Dave Jones
2006-01-04 21:40       ` [ck] 2.6.15-ck1 Radoslaw Szkodzinski
2006-01-05  0:12         ` 2.6.15-ck1 Con Kolivas
2006-01-05  0:27           ` 2.6.15-ck1 Dave Jones
2006-01-05  0:49             ` 2.6.15-ck1 Con Kolivas
2006-01-05  1:14               ` 2.6.15-ck1 Dave Jones
2006-01-05  1:22       ` 2.6.15-ck1 Andi Kleen
2006-01-05  1:36         ` 2.6.15-ck1 Con Kolivas
2006-01-05  6:04         ` 2.6.15-ck1 Dave Jones
2006-01-05  6:42         ` 2.6.15-ck1 Vojtech Pavlik
2006-01-05  6:55           ` [ck] 2.6.15-ck1 Con Kolivas
2006-01-05 15:19           ` 2.6.15-ck1 Andi Kleen
2006-01-05 16:30             ` 2.6.15-ck1 Vojtech Pavlik
2006-01-05 16:39               ` 2.6.15-ck1 Andi Kleen
2006-01-05 17:13                 ` 2.6.15-ck1 Dmitry Torokhov
2006-01-05 17:28                   ` 2.6.15-ck1 Andi Kleen
2006-01-05  1:50       ` 2.6.15-ck1 Tony Lindgren
2006-01-04 23:10     ` 2.6.15-ck1 Con Kolivas
2006-01-05  1:57       ` 2.6.15-ck1 Tony Lindgren
2006-01-05 18:47       ` [ck] 2.6.15-ck1 Kevin Radloff
2006-01-12 18:51         ` Daniel Petrini
2006-01-04 20:38   ` 2.6.15-ck1 Grant Coady
2006-01-04 20:56     ` 2.6.15-ck1 Dave Jones
2006-01-12 22:11   ` 2.6.15-ck1 Adam Belay
2006-01-12 23:03     ` 2.6.15-ck1 Dave Jones
2006-01-13  0:42       ` Adam Belay [this message]
2006-01-13  0:46         ` 2.6.15-ck1 Dave Jones
2006-01-16 20:28       ` 2.6.15-ck1 Ben Slusky
2006-01-14  3:42   ` 2.6.15-ck1 Philipp Rumpf
2006-01-14  4:41     ` 2.6.15-ck1 Dave Jones
2006-01-14 13:06       ` [ck] 2.6.15-ck1 Jens Axboe
2006-01-05 17:58 ` 2.6.15-ck1 Tomasz Torcz
2006-01-05 23:22   ` 2.6.15-ck1 Con Kolivas
2006-01-07 13:16     ` 2.6.15-ck1 Tomasz Torcz
     [not found]       ` <9268368b0601131119n639c345cgcf2a5dadd7cb423c@mail.gmail.com>
2006-01-14 20:54         ` 2.6.15-ck1 Tomasz Torcz

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=20060113004236.GB11601@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=ck@vds.kolivas.org \
    --cc=davej@redhat.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox