From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jeff@garzik.org>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
linux-scsi@vger.kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
edwintorok@gmail.com, axboe@kernel.dk
Subject: Re: [patch 2/4] Expose Power Management Policy option to users
Date: Wed, 01 Aug 2007 12:06:21 -0500 [thread overview]
Message-ID: <1185987981.3468.91.camel@localhost.localdomain> (raw)
In-Reply-To: <20070801165352.GB21219@parisc-linux.org>
On Wed, 2007-08-01 at 10:53 -0600, Matthew Wilcox wrote:
> On Tue, Jul 31, 2007 at 09:18:08AM -0500, James Bottomley wrote:
> > The other comment is that power saving seems to be a property of the
> > transport rather than the host. If you do it in the transport classes,
> > then you can expose all the knobs the actual transport possesses (which
> > is, unfortunately, none for quite a few SCSI transports).
>
> Would it save any power to negotiate down to, say, FAST-20 for the SPI
> transport? Or to negotiate narrow instead of wide, so fewer cables have
> to be powered?
Mechanically, I don't believe so. I'm not sure I can find any reports
on it; however, I believe the power wastage SPI comes from the
transcievers and terminators. There's the passive power from simply
powering the resistive bus and then the RMS power from sending commands
over an impedance circuit. simple physics on a 5v bus tells me that the
former is likely to be far greater than the latter. Finally, if you
think about what the bus is doing during signalling, the power drain is
independent of the frequency so I think the faster you squirt your data,
the lower the energy drain (hence high speed busses are actually lower
energy than low speed ones if the number of bits you have to transfer
remains constant).
James
next prev parent reply other threads:[~2007-08-01 17:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070705194909.337398431@intel.com>
2007-07-05 20:05 ` [patch 1/4] Store interrupt value Kristen Carlson Accardi
2007-08-01 8:18 ` Tejun Heo
2007-08-01 14:01 ` Jeff Garzik
2007-08-01 21:18 ` Kristen Carlson Accardi
2007-07-05 20:05 ` [patch 2/4] Expose Power Management Policy option to users Kristen Carlson Accardi
2007-07-09 19:36 ` Pavel Machek
2007-07-11 16:51 ` Kristen Carlson Accardi
2007-07-30 16:32 ` Jeff Garzik
2007-07-31 6:27 ` Tejun Heo
2007-07-31 14:16 ` Arjan van de Ven
2007-07-31 14:45 ` Tejun Heo
2007-07-31 16:15 ` Arjan van de Ven
2007-07-31 18:29 ` Tejun Heo
2007-08-01 9:23 ` Tejun Heo
2007-08-01 16:31 ` Kristen Carlson Accardi
2007-08-01 21:16 ` Kristen Carlson Accardi
2007-08-09 16:10 ` Kristen Carlson Accardi
2007-07-31 16:18 ` Kristen Carlson Accardi
2007-07-31 17:48 ` Tejun Heo
2007-07-31 20:24 ` Kristen Carlson Accardi
2007-08-01 3:20 ` Tejun Heo
2007-07-31 14:58 ` Tejun Heo
2007-07-31 14:18 ` James Bottomley
2007-08-01 16:53 ` Matthew Wilcox
2007-08-01 17:06 ` James Bottomley [this message]
2007-07-31 16:30 ` Kristen Carlson Accardi
2007-07-31 18:02 ` Tejun Heo
2007-07-31 19:58 ` Kristen Carlson Accardi
2007-08-01 3:24 ` Tejun Heo
2007-08-01 15:52 ` Kristen Carlson Accardi
2007-08-01 21:07 ` Kristen Carlson Accardi
2007-07-05 20:05 ` [patch 3/4] Enable link power management for ata drivers Kristen Carlson Accardi
2007-07-05 22:33 ` Andrew Morton
2007-07-05 22:37 ` Andrew Morton
2007-07-06 0:01 ` Jeff Garzik
2007-07-06 0:02 ` Jeff Garzik
2007-07-06 0:17 ` Andrew Morton
2007-07-06 0:00 ` Jeff Garzik
2007-08-01 8:27 ` Tejun Heo
2007-08-01 9:45 ` edwintorok
2007-08-01 21:11 ` Kristen Carlson Accardi
2007-08-02 5:27 ` Tejun Heo
2007-07-05 20:05 ` [patch 4/4] Enable Aggressive Link Power management for AHCI controllers Kristen Carlson Accardi
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=1185987981.3468.91.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=edwintorok@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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;
as well as URLs for NNTP newsgroup(s).