netdev - Re: [linux-pm] [RFC] Runtime power management on ipw2100

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 31 Jan 2007 13:53:20 +0200
From:	Amit Kucheria <amit.kucheria@...ia.com>
To:	ext Andi Kleen <ak@...e.de>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	ipw2100-devel@...ts.sourceforge.net, linux-pm@...ts.osdl.org,
	netdev@...r.kernel.org
Subject: Re: [linux-pm] [RFC] Runtime power management on	ipw2100

On Wed, 2007-01-31 at 11:48 +0100, ext Andi Kleen wrote:
> On Wednesday 31 January 2007 11:27, Matthew Garrett wrote:
> > On Wed, Jan 31, 2007 at 12:13:04PM +0100, Andi Kleen wrote:
> > > Matthew Garrett <mjg59@...f.ucam.org> writes:
> > > > 
> > > > PCI seems to require a delay of 10ms when sequencing from D3 to D0, 
> > > > which probably isn't acceptable latency for an "up" state.
> > > 
> > > It might be if the interface has been idle for some time
> > > (and the delay is not busy looping of course)
> > 
> > Hm. How would this interact with receiving packets?
> 
> The hardware will hopefully have support to wake itself up when that 
> happens.

Yes. Low power states without ability to respond to wakeup interrupts
would be broken behaviour generally.

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html