linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Tejun Heo <htejun@gmail.com>, Gabor FUNK <FUNK.Gabor@hunetkft.hu>,
	linux-ide@vger.kernel.org, Jim Paris <jim@jtan.com>
Subject: Re: sata_sil24 stability and performance
Date: Sun, 16 Mar 2008 23:09:33 -0400	[thread overview]
Message-ID: <47DDE0ED.6040304@rtr.ca> (raw)
In-Reply-To: <20080315214347.GA1511@denix.org>

Denys Dmytriyenko wrote:
>
> 1. Keep existing system, but utilize 2 PCI-X slots for SATA controllers. This 
> requires using 8-port adapters, like the one I already have Supermicro Marvell 
> based. The question is - how stable sata_mv these days? It still says HIGHLY 
> EXPERIMENTAL...
..

It will lose that status early in the 2.6.26 timeframe.

Currently it does seem to work reasonably, with NCQ even,
but there are still errata for me to get round to fixing,
and the IRQ/EH/Reset code needs some work to ensure it can
always recover when something weird happens.

Port multiplier support is working now, and will be pushed
for 2.6.26 along with other fixes and stuff.

ATAPI support may yet follow before the summer.

Cheers

-ml

  reply	other threads:[~2008-03-17  3:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19  2:09 sata_sil24 stability and performance Denys Dmytriyenko
2008-02-19  4:36 ` Jim Paris
2008-02-19  6:39   ` Denys Dmytriyenko
2008-02-19 15:32   ` Mark Lord
2008-03-02  6:14     ` Denys Dmytriyenko
2008-03-02  9:39       ` Gabor FUNK
2008-03-04  0:02         ` Tejun Heo
2008-03-04  0:22           ` Denys Dmytriyenko
2008-03-04  3:28             ` Tejun Heo
2008-03-04  6:29               ` Denys Dmytriyenko
2008-03-05  8:11                 ` Tejun Heo
2008-03-06  4:14                   ` Denys Dmytriyenko
2008-03-06  4:25                     ` Tejun Heo
2008-03-06  6:55                       ` Denys Dmytriyenko
2008-03-06  7:08                         ` Tejun Heo
2008-03-15 21:43                           ` Denys Dmytriyenko
2008-03-17  3:09                             ` Mark Lord [this message]
2008-03-18  0:15                               ` Denys Dmytriyenko
2008-03-18  4:09                                 ` Tejun Heo
2008-03-18  4:53                                   ` Denys Dmytriyenko
2008-03-18  6:40                                     ` Tejun Heo
2008-03-20 22:37                                       ` Denys Dmytriyenko
2008-03-21  0:18                                         ` Tejun Heo
2008-04-14  1:19                                           ` Denys Dmytriyenko
2008-04-14  2:49                                             ` Tejun Heo
2008-04-14 10:55                                             ` Gabor FUNK
2008-03-18  9:14                                     ` Gabor FUNK
2008-03-18 13:06                                       ` Gabor FUNK
2008-03-18 20:05                                   ` Mark Lord
2008-03-18 20:06                                     ` Mark Lord

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=47DDE0ED.6040304@rtr.ca \
    --to=liml@rtr.ca \
    --cc=FUNK.Gabor@hunetkft.hu \
    --cc=denis@denix.org \
    --cc=htejun@gmail.com \
    --cc=jim@jtan.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).