linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	James.Bottomley@steeleye.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:24:44 +0900	[thread overview]
Message-ID: <46AFFCFC.7020902@gmail.com> (raw)
In-Reply-To: <20070731125849.501443c1.kristen.c.accardi@intel.com>

Kristen Carlson Accardi wrote:
>> I don't think the interface you're suggesting is a good one.  Do you?
> 
> I think if it's applicable to SCSI at all it is fine.  If it is not, then
> I think we need to make do with the interface we are given.  I do not think
> we should hold up a feature for libata sysfs integration.

Well, I guess we'll have to agree to disagree here and leave the
decision to James and Jeff.

>>> I can assert that I think ALPM is a good idea,
>>> because I've never had a report of it causing problems.  Windows has 
>>> been using this feature for a very long time - and you have to admit that
>>> they have a pretty large market share.  Nobody is complaining about ALPM
>>> increasing device malfunction, so unless you have proof it seems insane
>>> to nak due to this. 
>> Is ALPM enabled by default?  How do they deal with the performance
>> degradation?
> 
> I believe so, but I'm obviously not privvy to their implementation details.

It would be *really* great if we can find more about how they do it.
How and when it's enabled and on which systems.  Is it possible to find
this out?

-- 
tejun

  reply	other threads:[~2007-08-01  3:25 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
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 [this message]
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=46AFFCFC.7020902@gmail.com \
    --to=htejun@gmail.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=edwintorok@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 \
    /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).