All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Tejun Heo <tj@kernel.org>,
	linux-ide@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] libata: Add ALPM power state accounting to the AHCI driver
Date: Mon, 16 Nov 2009 16:25:34 -0500	[thread overview]
Message-ID: <4B01C34E.9050607@pobox.com> (raw)
In-Reply-To: <20091116072114.65c6fbc2@infradead.org>

On 11/16/2009 10:21 AM, Arjan van de Ven wrote:
> On Mon, 16 Nov 2009 23:59:39 +0900
> Tejun Heo<tj@kernel.org>  wrote:
>
>> Arjan van de Ven wrote:
>>> is there a hardware way to ask for the link status via a link level
>>> thing? I thought the sata_scr_read() was by definition a host thing
>>
>> sata_scr_read() will do the right thing given the link parameter
>> although it needs to be called from EH context for PMP links.  For
>> now, just making the functions take @link param and passing it around
>> should do.
>>
>
> I'm sorry it just does not make sense to me anymore.
> if this moves to be a link level thing, then the statistics also need
> to be kept link level, and thus exported link level, and I don't think
> that exists.

It is already link-level in hardware (ie. in reality), in the sata_scr_* 
interface, and in the accounting stats you [quite correctly] added to 
struct ata_link in your patch.

The only thing -not- at link level is the userland interface, which 
instead uses host-level granularity.

	Jeff



  parent reply	other threads:[~2009-11-16 21:25 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
2009-11-16 21:25                                 ` Jeff Garzik [this message]
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=4B01C34E.9050607@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --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 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.