From: Florian Weimer <fw@deneb.enyo.de>
To: Lawrence Walton <lawrence@the-penguin.otak.com>
Cc: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables
Date: Tue, 01 Nov 2005 18:13:59 +0100 [thread overview]
Message-ID: <87wtjs8f54.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20051101170413.GA11640@the-penguin.otak.com> (Lawrence Walton's message of "Tue, 1 Nov 2005 09:04:13 -0800")
* Lawrence Walton:
>> In my experience, the 3ware SATA controllers which are not NCQ-capable
>> have very, very lousy write performance with some drives, unless you
>> enable the write cache (which is, of course, a bit dangerous without
>> UPS or battery backup on the controller).
> Not to sound like the a 3ware chearleader, but this card does support NCQ.
Oh. I didn't know whether this particukar controller supported NCQ or
not.
BTW, does anybody know if NCQ support is available for the 9500S in a
firmware upgrade?
next prev parent reply other threads:[~2005-11-01 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 21:10 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables Alex Bligh - linux-kernel
2005-11-01 12:45 ` Florian Weimer
2005-11-01 17:04 ` Lawrence Walton
2005-11-01 17:13 ` Florian Weimer [this message]
2005-11-02 0:11 ` Alex Bligh - linux-kernel
2005-11-01 22:54 ` Jeff V. Merkey
2005-11-02 22:39 ` Alex Bligh - linux-kernel
[not found] <BEDEA151E8B1D6CEDD295442@192.168.100.25>
2005-11-02 22:59 ` adam radford
2005-11-05 9:06 ` Alex Bligh - linux-kernel
2005-11-05 17:01 ` Jeff V. Merkey
2005-11-07 21:53 ` Florian Weimer
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=87wtjs8f54.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=lawrence@the-penguin.otak.com \
--cc=linux-kernel@alex.org.uk \
--cc=linux-kernel@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