From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: ops->qc_defer not invoked on ata_exec_internal_sg() paths ?
Date: Tue, 26 Feb 2008 10:37:31 +0900 [thread overview]
Message-ID: <47C36D5B.7080600@gmail.com> (raw)
In-Reply-To: <47C35B6B.8000406@rtr.ca>
Hello, Mark.
Mark Lord wrote:
> The optional .qc_defer() methods don't seem to be called
> on the ata_exec_internal_sg() path.
>
> At present, this is probably okay. But in the future,
> as we add functionality for link power management
> and hotplug polling, this could be a problem.
>
> I think. Or is it possibly also a problem today
> for sata_send_pmp() and friends ?
That's intentional and okay. Currently, EH can only issue one non-NCQ
command at a time and dynamic link PM and hotplug polling shouldn't be
done via EH anyway. EH is way too big a hammer for those.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-02-26 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 0:20 ops->qc_defer not invoked on ata_exec_internal_sg() paths ? Mark Lord
2008-02-26 1:37 ` Tejun Heo [this message]
2008-02-26 12:32 ` Alan Cox
2008-02-26 15:47 ` Mark Lord
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=47C36D5B.7080600@gmail.com \
--to=htejun@gmail.com \
--cc=liml@rtr.ca \
--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 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).