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-next>] [day] [month] [year] [list]
Message-Id: <20070705130357.1c172b80.kristen.c.accardi@intel.com>
Date:	Thu, 5 Jul 2007 13:03:57 -0700
From:	Kristen Carlson Accardi <kristen.c.accardi@...el.com>
To:	jeff@...zik.org
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org, James.Bottomley@...eleye.com,
	edwintorok@...il.com, axboe@...nel.dk, linux-scsi@...r.kernel.org
Subject: [patch 0/4] SATA power savings patches (ALPM)

Hi Jeff,
Here's the most recent patches for ALPM.  These are also located at:
http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm

These patches implement Aggressive Link Power management for AHCI 
controllers.  This feature is described in detail in the AHCI 1.x spec.
It provides power savings of anywhere from .5-1.5 Watts depending on
the system when it is enabled.  (a graph demonstrating power savings
of this patch along with other power patches is located at 
http://www.linuxpowertop.org/results.php for your enjoyment).

This patch is changed from the previous version in that it incorporates all
the feedback I've gotten on the patches to date.  It changes the default
of the ahci driver to be max_performance rather than min_power, so userspace
will need to explicitly enable alpm via the sysfs interface when it deems
it an appropriate time to do this.  In addition, the patch was changed to
allow either HIPM or DIPM as a prerequisite for enabling ALPM, rather than 
just using HIPM.

Thanks,
Kristen
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ