linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-ide@vger.kernel.org
Subject: Re: sata_nv on MCP51: NCQ possible?
Date: Thu, 15 Nov 2007 12:09:21 +0300	[thread overview]
Message-ID: <473C0CC1.3090702@msgid.tls.msk.ru> (raw)
In-Reply-To: <473C0AB1.8050907@msgid.tls.msk.ru>

[replying to myself...]

Michael Tokarev wrote:
> While trying to test NCQ thing again, I come across
> a problem, it seems: the only hardware available for
> testing to me right now is an ASUS M2NPV-VM motherboard,
> which is based on Nvidia nForce 430/GeForce 6150.
> lspci shows this:
> 
>  00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
> 
> I see no command queuing enabled by linux (queue depth: 0/32),
> and there's no way to enable it in sysfs, either.

Hmm.  When googling harder, I've found something about this,
e.g. here:

http://www.mail-archive.com/linux-ide@vger.kernel.org/msg09517.html

(it's a long thread).

But some question(s) remains still.

First, it looks like that patch(set) isn't in 2.6.23.  I'll grab
2.6.24pre to see if it's there.

And second, and most important -- what's "SW NCQ", or "Software NCQ"?
To me it sounds like "BIOS RAID" - that "RAID" thing found on many
modern desktop motherboards which isn't hardware raid, and hence
it does not offer any advantage over normal linux software raid
implementation (which has its own advantages anyway).  So I'm
a bit confused here: linux I/O scheduler and this "Software NCQ" -
isn't one of the two redundrand?  And sure thing - is it worth
to test NCQ at all if it's "Software"?

Thanks.

/mjt

      reply	other threads:[~2007-11-15  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  9:00 sata_nv on MCP51: NCQ possible? Michael Tokarev
2007-11-15  9:09 ` Michael Tokarev [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=473C0CC1.3090702@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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).