From: Arjan van de Ven <arjan@linux.intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org, len.brown@intel.com
Subject: Re: [RFC] maximum latency tracking infrastructure
Date: Fri, 25 Aug 2006 10:19:45 +0200 [thread overview]
Message-ID: <1156493985.3032.13.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060824222417.GA27504@srcf.ucam.org>
On Thu, 2006-08-24 at 23:24 +0100, Matthew Garrett wrote:
> 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?
first of all that 500 is a bit of a guess on my side; James (the Intel
wireless guy) is on holiday so I couldn't get real numbers out of it.
But as proof of concept it's pretty ok :)
> 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?
the "problem" is that bioses lie about these numbers all the time as
well ;( (it's getting better but still).
Those numbers you gave, were those on batter or on AC ? (apparently for
the problem machines C3 latency goes WAY up when on battery, and then
the problem hits)
next prev parent reply other threads:[~2006-08-25 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 17:41 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
2006-08-25 8:19 ` Arjan van de Ven [this message]
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=1156493985.3032.13.camel@laptopd505.fenrus.org \
--to=arjan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®