From: Arjan van de Ven <arjan@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] libata: Add ALPM power state accounting to the AHCI driver
Date: Sun, 15 Nov 2009 21:55:31 -0800 [thread overview]
Message-ID: <20091115215531.23edcf5e@infradead.org> (raw)
In-Reply-To: <4B00B5D0.4010707@kernel.org>
On Mon, 16 Nov 2009 11:15:44 +0900
Tejun Heo <tj@kernel.org> wrote:
> > Moving the base accounting logic to libata wasn't too painful (see
> > the patch); moving this very driver specific logic gets a much more
> > intertwigned relationship that at this point in time is just
> > overkill. If someone comes around with a driver that also need it,
> > can we just please resolve it at that time?
>
> I don't know. On PM front, it's true that ahci is way more important
> than others. Implementing things just for ahci has been happening for
> some time now and in the long run it's just not healthy. It lowers
> maintainability and may even hinder generic implementation. In this
> case, for example, you're associating link power management with the
> host port, not the link. Your specific case may be fine but what
> about DIPM on devices attached via PMP? Internal implementation is
> one thing but you're adding externally visible attribute to the host
> part. This one thing might be fine but we can't allow things like
> this to pile up.
sigh. so I moved all the generic logic generic, and left the ahci
specific code specific to ahci. I put the logic there where it was
easy to implement, and there where the other link power management
controls are (in sysfs). If that's not good enough, I'm out of my skills
in the libata world to be honest, and would like to ask you to implement
that instead. let me know what sysfs looks like and I'll adjust
powertop to it....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-11-16 5:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 3:24 [PATCH] libata: Add ALPM power state accounting to the AHCI driver Arjan van de Ven
2009-11-15 8:05 ` Tejun Heo
2009-11-15 8:27 ` Jeff Garzik
2009-11-15 17:46 ` Arjan van de Ven
2009-11-15 18:06 ` Tejun Heo
2009-11-15 18:23 ` Arjan van de Ven
2009-11-15 18:26 ` Tejun Heo
2009-11-15 18:33 ` Arjan van de Ven
2009-11-16 1:51 ` Tejun Heo
2009-11-16 2:00 ` Arjan van de Ven
2009-11-16 2:15 ` Tejun Heo
2009-11-16 5:55 ` Arjan van de Ven [this message]
2009-11-16 6:14 ` Tejun Heo
2009-11-16 8:13 ` Jeff Garzik
2009-11-16 14:43 ` Arjan van de Ven
2009-11-16 14:59 ` Tejun Heo
2009-11-16 15:21 ` Arjan van de Ven
2009-11-16 15:35 ` Tejun Heo
2009-11-16 15:40 ` Tejun Heo
2009-11-16 15:57 ` Alan Cox
2009-11-16 16:25 ` Tejun Heo
2009-11-16 21:25 ` Jeff Garzik
2009-11-16 21:21 ` Jeff Garzik
2009-11-17 5:25 ` Arjan van de Ven
2009-11-15 17:00 ` Arjan van de Ven
2009-11-15 18:36 ` Arjan van de Ven
2009-11-15 18:42 ` Arjan van de Ven
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=20091115215531.23edcf5e@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).