From: Mogens Valentin <monz@danbbs.dk>
To: Linux-scsi <linux-scsi@vger.kernel.org>
Subject: Ultra160 controller on 32bit pci
Date: Thu, 06 May 2004 10:15:04 +0200 [thread overview]
Message-ID: <4099F408.E424C26A@danbbs.dk> (raw)
Currently using Adaptec 29160, works fine, but it's only 160/2, after
all.
I'm curious if other controllers can provide better performance when
used on a 32bit pci bus?
In a few month I might switch to a pci-express/opteron setup, so I'd
like some indication about controllers for that bus.
I'm using two u320 10K disks + one fast10 device on a development
server/workstation, so I don't need an interprise-level ctrl.; but both
the pci32 and pci-express thingy should preferebly provide a narrow
connector as well.
I'm not currently on the scsi list, so if anyone would care to shed some
lights, please address me directly.
Thanks.
--
Kind regards,
Mogens Valentin
Networking, Security
www.danbbs.dk/~monz
Phone +45 32 525 878
next reply other threads:[~2004-05-06 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 8:15 Mogens Valentin [this message]
2004-05-06 15:29 ` Ultra160 controller on 32bit pci Matthew Wilcox
2004-05-06 15:51 ` Mogens Valentin
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=4099F408.E424C26A@danbbs.dk \
--to=monz@danbbs.dk \
--cc=linux-scsi@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