public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [PATCH] SATA NCQ support
Date: Fri, 27 May 2005 16:58:21 +0200	[thread overview]
Message-ID: <20050527145821.GX1435@suse.de> (raw)
In-Reply-To: <429732CE.5010708@gmx.de>

On Fri, May 27 2005, Matthias Andree wrote:
> Jens Axboe wrote:
> 
> > NCQ requires hardware support from both the controller and hard drive,
> > you can view Jeff's libata status page for which controllers support
> > NCQ.
> 
> So that means controllers that do not support either NCQ or HBQ just

Forget host based queueing, it's worthless. The device needs knowledge
of the pending commands to eliminate rotational delay, which is
basically the real win of command queueing.

> suck and should not be cared about, and if I were to go into SATA, I
> should just get a new controller and forget about my onboard VIA crap.
> (I read newer VIA are supposed to support AHCI which is good.)

SATA is still pretty fast without NCQ, it just makes some operations a
lot faster. But of course if you want the best, you would opt for some
setup that allows NCQ. To my knowledge, ahci compliance doesn't
guarantee NCQ support (the adapter flags it in its host capability
flags), so I don't know if the newer VIA will get you NCQ support.

People have lived happily without NCQ support in SATA for years, I'm
sure you could too :-)

-- 
Jens Axboe


  reply	other threads:[~2005-05-27 14:57 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
2005-05-27 14:46     ` Matthias Andree
2005-05-27 14:58       ` Jens Axboe [this message]
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=20050527145821.GX1435@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