From: Lin Ming <ming.m.lin@intel.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Priyanka Gupta <ankaguptaca@gmail.com>,
"Zhang, Rui" <rui.zhang@intel.com>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [RFC] ata port runtime pm
Date: Fri, 28 Oct 2011 13:36:34 +0800 [thread overview]
Message-ID: <1319780194.24236.34.camel@minggr> (raw)
In-Reply-To: <4EAA2392.40105@pobox.com>
On Fri, 2011-10-28 at 11:37 +0800, Jeff Garzik wrote:
> On 10/27/2011 11:21 PM, Lin Ming wrote:
> > @@ -3208,6 +3209,11 @@ int ata_scsi_queuecmd(struct Scsi_Host *shost, struct scsi_cmnd *cmd)
> >
> > ap = ata_shost_to_port(shost);
> >
> > + if (pm_runtime_suspended(&ap->tdev))
> > + pm_runtime_resume(&ap->tdev);
> > + pm_runtime_mark_last_busy(&ap->tdev);
> > + pm_request_autosuspend(&ap->tdev);
> > +
> > spin_lock_irqsave(ap->lock, irq_flags);
> >
>
>
> Putting this into the core command dispatch fast-path is rather
> disappointing. That's at least one additional lock, plus some atomic
> instructions and tests.
Maybe move suspend request to the resume function, as below.
static int ata_port_runtime_resume(struct device *dev)
{
struct ata_port *ap = to_ata_port(dev);
int rc;
rc = ata_port_request_pm(ap, PMSG_ON, ATA_EH_RESET,
ATA_EHI_NO_AUTOPSY | ATA_EHI_QUIET, 1);
pm_runtime_mark_last_busy(dev);
pm_request_autosuspend(dev);
return rc;
}
Then the fast-path looks like,
@@ -3208,6 +3209,9 @@ int ata_scsi_queuecmd(struct Scsi_Host *shost,
struct scsi_cmnd *cmd)
ap = ata_shost_to_port(shost);
+ if (pm_runtime_suspended(&ap->tdev))
+ pm_runtime_resume(&ap->tdev);
+
spin_lock_irqsave(ap->lock, irq_flags);
ata_scsi_dump_cdb(ap, cmd);
What do you think?
Thanks,
Lin Ming
next prev parent reply other threads:[~2011-10-28 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 3:21 [RFC] ata port runtime pm Lin Ming
2011-10-28 3:37 ` Jeff Garzik
2011-10-28 5:36 ` Lin Ming [this message]
2011-10-28 17:31 ` Rafael J. Wysocki
2011-10-28 18:51 ` Alan Stern
2011-11-01 8:12 ` Lin Ming
2011-11-01 19:34 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2011-10-28 3:20 Lin Ming
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=1319780194.24236.34.camel@minggr \
--to=ming.m.lin@intel.com \
--cc=ankaguptaca@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
--cc=tj@kernel.org \
--cc=ying.huang@intel.com \
/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).