All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Arjan van de Ven <arjan@infradead.org>,
	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: Tue, 17 Nov 2009 01:25:15 +0900	[thread overview]
Message-ID: <4B017CEB.7050309@kernel.org> (raw)
In-Reply-To: <20091116155734.13912158@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> This is true for all link functions, so I'm suggesting the stats
>> helpers to follow the same convention.  This will also make slave link
>> configuration work properly (controllers which present two SATA links
>> as master/slave of the same port but still provide access to separate
>> SCR registers).  You know, it's a link function, make it take a link
>> as all other stuff is designed that way.
> 
> I don't see how you can do per link reporting on AHCI.
> 
> Sure maybe some devices should expose it per link, but it's so expensive
> and it'll get really ugly fast.

Not for ahci but ata_piix, sis and via already do it.

> I'd say it has to go in at host level for now. If some super whizzo
> future silicon exposes it per link without being beaten around the head
> by the software stack then it's easy enough to add per link data and a
> generic helper which provides a summary set of numbers at the host level
> for hardware that can report link data.
> 
> That gives us a useful API now and the ability to fix it in the future,
> not that I anticipate anyone ever needing to. AHCI (or AHCI-ish) seems to
> be what everyone is working to nowdays with little obvious pressure to
> move anywhere else.

Yeap, agreed.  It just is so ugly (not Arjan's fault).

Thanks.

-- 
tejun

  reply	other threads:[~2009-11-16 16:26 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
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 [this message]
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=4B017CEB.7050309@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.