public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, len.brown@intel.com
Subject: Re: [RFC] maximum latency tracking infrastructure
Date: Thu, 24 Aug 2006 23:24:18 +0100	[thread overview]
Message-ID: <20060824222417.GA27504@srcf.ucam.org> (raw)
In-Reply-To: <1156441295.3014.75.camel@laptopd505.fenrus.org>

On Thu, Aug 24, 2006 at 07:41:35PM +0200, Arjan van de Ven wrote:

> +	/* the ipw2100 hardware really doesn't want power management delays
> +	 * longer than 500usec
> +	 */
> +	modify_acceptable_latency("ipw2100", 500);
> +

Hm. My BIOS claims that the C3 transition period is 85usec (and even my 
C4 is 185) , but I've hit the error path where C3 gets disabled. Is this 
really adequate? Also, by the looks of it, the C3 disabling path is 
still present - is it still theoretically necessary with the above, or 
is this just a belt and braces approach?

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

  parent reply	other threads:[~2006-08-24 22:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 17:41 [RFC] maximum latency tracking infrastructure Arjan van de Ven
2006-08-24 19:18 ` Len Brown
2006-08-24 21:08 ` Jesse Barnes
2006-08-24 21:20   ` Arjan van de Ven
2006-08-24 21:29     ` Jesse Barnes
2006-08-24 21:50       ` Andi Kleen
2006-08-25  4:54     ` Nick Piggin
2006-08-25  7:58       ` Arjan van de Ven
2006-08-25  8:26         ` Nick Piggin
2006-08-25  8:30           ` Arjan van de Ven
2006-08-24 21:52 ` Daniel Walker
2006-08-24 21:57   ` Arjan van de Ven
2006-08-24 22:16     ` Daniel Walker
2006-08-24 22:24 ` Matthew Garrett [this message]
2006-08-25  8:19   ` Arjan van de Ven
2006-08-24 22:52 ` Matt Mackall
2006-08-25  7:56   ` Arjan van de Ven
2006-08-25 14:54     ` Matt Mackall

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=20060824222417.GA27504@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=arjan@linux.intel.com \
    --cc=len.brown@intel.com \
    --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