From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>,
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:47:42 -0500 [thread overview]
Message-ID: <47C4349E.5010802@rtr.ca> (raw)
In-Reply-To: <20080226123209.7ca9eed4@core>
Alan Cox wrote:
> On Mon, 25 Feb 2008 19:20:59 -0500
> Mark Lord <liml@rtr.ca> 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.
>
> It becomes a problem for me certainly if we ever issue anything via
> exec_internal_sg while another command may be outstanding anywhere on the
> same *host*. Right now its ok.
..
Yeah, for serializing a pair of ATA channels on the same host chip.
-ml
prev parent reply other threads:[~2008-02-26 15:44 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
2008-02-26 12:32 ` Alan Cox
2008-02-26 15:47 ` Mark Lord [this message]
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=47C4349E.5010802@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.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 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).