Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754185Ab0FVThX (ORCPT ); Tue, 22 Jun 2010 15:37:23 -0400 Received: from mail-pw0-f46.google.com ([209.85.160.46]:58409 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752478Ab0FVThW convert rfc822-to-8bit (ORCPT ); Tue, 22 Jun 2010 15:37:22 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=mwM5yUgQejJTQZ8prtfS3ryWRM7hsGv8AG/qxWavmByN5m2+uEsIlRz2UQ1YV7vI3l TOMtDhvOZrabjPxOff1g88SHfs82LsKWhgh0duFO/MCmMqUmZXd7Ch8Pauno5jmQnVhs vLXA9yR8aVk5nMV2btgjxWMNeasXqBZpZDfJ4= MIME-Version: 1.0 In-Reply-To: <20100622193143.GA17803@sig21.net> References: <20100622163138.GD20668@srcf.ucam.org> <20100622165213.GA21842@srcf.ucam.org> <20100622172545.GA22680@srcf.ucam.org> <20100622175058.GA23499@srcf.ucam.org> <20100622184426.GA24546@srcf.ucam.org> <20100622193143.GA17803@sig21.net> From: "Luis R. Rodriguez" Date: Tue, 22 Jun 2010 12:37:01 -0700 Message-ID: Subject: Re: [ath5k-devel] [PATCH v2] ath5k: disable ASPM To: Johannes Stezenbach Cc: Matthew Garrett , Jussi Kivilinna , Maxim Levitsky , David Quan , Bob Copeland , "Luis R. Rodriguez" , ath5k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org, linux-kernel , Jonathan May , Tim Gardner Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2651 Lines: 53 On Tue, Jun 22, 2010 at 12:31 PM, Johannes Stezenbach wrote: > On Tue, Jun 22, 2010 at 07:44:26PM +0100, Matthew Garrett wrote: >> On Tue, Jun 22, 2010 at 11:28:20AM -0700, Luis R. Rodriguez wrote: >> > >> > Heh, this whole patch and thread was started because Jussi tested >> > ath5k with  pcie_aspm=force (on a pre PCIE 1.1 device (?)) . I have >> > been trying to explain all along why this is a terrible idea to the >> > point we should probably just remove that code from the kernel. Hence >> > my side rants and explanations to justify my reasonings. >> >> Well, there's two things here. If you use force then you might get >> inappropriate ASPM. But if your BIOS enables ASPM on an old device, then >> booting *without* CONFIG_PCIE_ASPM will leave it turned on, and booting >> *with* CONFIG_PCIE_ASPM will turn it off. The Kconfig description is >> confusing - reality is that CONFIG_PCIE_ASPM enables logic that allows >> the kernel to modify the BIOS default, and disabling it makes the >> assumption that your BIOS did something sensible. > > Does CONFIG_PCIEASPM provide a way for the user to modifiy > the settings at runtime? You can tune ASPM settings at runtime, regardless of CONFIG_PCIEASPM. See: http://kernel.org/pub/linux/kernel/people/mcgrof/aspm/enable-aspm http://wireless.kernel.org/en/users/Documentation/ASPM > I have a Samsung N130 netbook which has a BIOS setting > called "CPU Power Saving Mode".  When enabled it activates > ASPM L1 and L0s for the ethernet chip (Realtek RTL8102e, 100Mbit) > and the PCIE bridge (with the BIOS setting off it's just L1). > The result is that the ethernet througput is reduced to 25Mbit/s. > (The BIOS setting does not activa L0s for the Atheros AR9285 WLAN.) > > 99,9% of the time I want to enjoy the power savings, > but occationally I have to transfer some bulk data and would > like to switch the setting for a few minutes. > > Or, well, ideally I'd like to have power savings _and_ performance > at the same time without any manual intervention.  I'm not sure > if this is a quirk of the N130 or if ASPM L0s always causes > performance degradation? L0s is not going to buy you much gains, getting at least L1 will however. L0s is just a further enhancement. I recommend you test by enabling L1 and L0s, check how longer your battery lasts and then test again with just L1. Then test without both L1 and L0s. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/