From: "H. Peter Anvin" <hpa@zytor.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Matthew Wilcox <matthew@wil.cx>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ultrastor.c is a bit-rot
Date: Sun, 23 Mar 2008 10:18:46 -0700 [thread overview]
Message-ID: <47E690F6.6030905@zytor.com> (raw)
In-Reply-To: <20080323171652.GF10722@ZenIV.linux.org.uk>
Al Viro wrote:
>
> ... not that VLB didn't suck badly with several devices attached at the same
> time. I would be rather surprised if that board would work if fully populated
> with VLB cards, all in active use. IOW, a likely explanation is that it
> had a warning along the lines of "use of more than <number> of VLB cards
> at the same time may use instability" buried in documentation and proud
> "6 VLB slots!!!" touted by marketing...
>
> I can't find VLB specs online, but IIRC 3 had been the limit and anything
> past that had been very much out of spec and likely to screw you.
I think that particular board had multiple root drivers (it was a P5
board, so it wasn't a "local" bus anyway.)
-hpa
next prev parent reply other threads:[~2008-03-23 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 14:59 ultrastor.c is a bit-rot Boaz Harrosh
2008-03-17 15:23 ` James Bottomley
2008-03-17 16:00 ` Boaz Harrosh
2008-03-17 16:03 ` James Bottomley
2008-03-17 17:01 ` Boaz Harrosh
2008-03-17 17:25 ` James Bottomley
2008-03-17 17:25 ` James Bottomley
2008-03-17 15:23 ` Matthew Wilcox
2008-03-21 20:41 ` H. Peter Anvin
2008-03-23 9:54 ` Boaz Harrosh
2008-03-23 16:24 ` H. Peter Anvin
2008-03-23 17:16 ` Al Viro
2008-03-23 17:18 ` H. Peter Anvin [this message]
2008-03-17 16:07 ` Alan Cox
2008-03-18 22:07 ` Benny Amorsen
2008-03-18 22:07 ` Benny Amorsen
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=47E690F6.6030905@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.