public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: linux-kernel@vger.kernel.org
Cc: matthias.andree@gmx.de, jgarzik@pobox.com
Subject: Re: [PATCH] SATA NCQ support
Date: Fri, 27 May 2005 15:53:00 +0200	[thread overview]
Message-ID: <20050527135258.GW1435@suse.de> (raw)
In-Reply-To: <20050527131842.GC19161@merlin.emma.line.org>


(please CC the folks in the thread!)

On Fri, May 27 2005, Matthias Andree wrote:
> On Fri, 27 May 2005, Jens Axboe wrote:
> 
> > Update the patch, it's against bleeding edge git (applies to 2.6.12-rc5
> > as well). Changes:
> > 
> > - (libata) Change to SCSI change_queue_depth API, kill current hack.
> > 
> > - (ahci) Move SActive bit set to ahci_qc_issue() where it belongs.
> 
> OK, so this is for AHCI. What are the options for people whose
> mainboards aren't blessed with AHCI, but use for instance VIA or older
> Promise chips? Buy new hardware? Or wait until someone comes up with an
> implementation?

NCQ requires hardware support from both the controller and hard drive,
you can view Jeff's libata status page for which controllers support
NCQ. via do not, some newer promise do iirc. Some siimage and qstor
support it as well.

Modifying a sata driver to support NCQ should be pretty trivial,
provided the hardware supports it (and docs are available, AHCI is
completely open).

> Can this queueing be emulated by software (libata or the libata chipset
> driver) or would such be mentioned in Jeff's list as "host-based
> queueing"?

Legacy queueing doesn't require support in the controller, however it's
not worth the effort to spend time on that. drivers/ide already had
support for that some time ago, it was ripped out again because it
sucked. IMHO, the only queueing worth supporting is NCQ. Queueing only
at the host level will not buy you anything.

-- 
Jens Axboe


  reply	other threads:[~2005-05-27 13:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27  7:03 [PATCH] SATA NCQ support Jens Axboe
2005-05-27  7:22 ` Jeff Garzik
2005-05-27  7:30   ` Jens Axboe
2005-05-27  7:37     ` Jeff Garzik
2005-05-27  7:47       ` Jens Axboe
2005-05-27  7:56         ` Jens Axboe
2005-05-27  8:24           ` Jeff Garzik
2005-05-27  8:27           ` Jeff Garzik
2005-05-27  8:28         ` Jeff Garzik
2005-05-27  8:35           ` Jens Axboe
2005-05-27  8:38             ` Jeff Garzik
2005-05-27  8:42               ` Jens Axboe
2005-05-27 23:47                 ` Jeff Garzik
2005-05-27 13:18 ` Matthias Andree
2005-05-27 13:53   ` Jens Axboe [this message]
2005-05-27 14:46     ` Matthias Andree
2005-05-27 14:58       ` Jens Axboe
2005-05-29 13:16         ` Matthias Andree
2005-05-29 16:36           ` Jeff Garzik
2005-05-30  2:35             ` Eric D. Mudama
2005-05-30  3:41         ` Greg Stark
2005-05-30  4:04           ` Eric D. Mudama
2005-05-30  6:21             ` Greg Stark
2005-05-30  6:33               ` Jens Axboe
2005-05-30 12:16                 ` Jens Axboe
2005-05-30 12:37                   ` Jens Axboe
2005-05-30 14:51                     ` Jens Axboe
2005-05-27 16:00   ` Jeff Garzik
     [not found] <48Hix-88s-7@gated-at.bofh.it>
     [not found] ` <48N4N-4B5-25@gated-at.bofh.it>
     [not found]   ` <48Pzt-6Kb-5@gated-at.bofh.it>
2005-05-31  0:00     ` Robert Hancock
2005-05-31  1:21       ` Jeff Garzik

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=20050527135258.GW1435@suse.de \
    --to=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    /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