From: Jeff Garzik <jgarzik@pobox.com>
To: Mat.Loikkanen@synopsys.com
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: SATA NCQ
Date: Wed, 02 Feb 2005 14:30:22 -0500 [thread overview]
Message-ID: <42012A4E.1020100@pobox.com> (raw)
In-Reply-To: <000401c50957$0e9d4600$3805040a@internal.synopsys.com>
Mat Loikkanen wrote:
> Jeff-
>
> Any word on when Native Command Queueing will be supported by Libata? I see
> in your status report there's a dependency on drives being available. As it
[snip, due to mailing list]
> implemented over in Windows?) ... I'd be available to work on adding NCQ
> support to Libata, but my unfamiliarity with the SCSI layer's workings may
> be a big hurdle. What do you think?
(cc'd to linux-ide, for others' information)
Well, you also need a controller that does DMA and NCQ, not just a
drive. NCQ is basically a handshaking protocol between the controller
and drive, letting the drive tell the controller when to DMA <x> sectors
from outstanding ATA command <y>.
No hard date on NCQ availability, and you are welcome (encouraged!) to
contribute NCQ support.
Adding NCQ support is
(a) telling the SCSI layer our queue depth
(b) handling more than one command outstanding at a time (libata should
be mostly ready for this, already)
(c) error handling
(c) is the hardest part. Getting working NCQ is easy ('a' and 'b'), but
making sure you recover correctly from errors is the biggest part of the
task.
That said... patches are always welcome!
Jeff
parent reply other threads:[~2005-02-02 19:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000401c50957$0e9d4600$3805040a@internal.synopsys.com>]
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=42012A4E.1020100@pobox.com \
--to=jgarzik@pobox.com \
--cc=Mat.Loikkanen@synopsys.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).