From: Mike Insch <vofka@hotpop.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oddities with HighPoint HPT374, 2.4.19-pre10-ac2
Date: Thu, 25 Jul 2002 14:10:57 +0100 [thread overview]
Message-ID: <200207251410.57227.vofka@hotpop.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10207250507480.4719-100000@master.linux-ide.org>
OK - Thanks for the Info.
For the moment, the machine in question will be simply running as a SAMBA
Server, and then only for one or two clients at a time (it's storing disk
images from PowerQuest's Drive Image Pro Software), and it (so far) seems to
be stable enough when data is coming in from the network.
If there is any detailed info. I can give you from the system, I'll be happy
to pop them over to you - similarly, if I can help test any revised versions
in the future, I'd be happy to do so.
Thanks again... :)
On Thursday 25 July 2002 13:25, Andre Hedrick wrote:
> The oddities are the fact I have not finished creating the channel and
> drive set inner-lock sequence code :-/ If you run it in master mode only
> one drive per channel, it is perfectly safe. The problem happens the
> instant you pair drives on the channels. I have not figured out the
> correct interrupt sequence ordering and blocking recipe.
>
> The issue stands to deal with double hwgroups locking and having more than
> two channels to the effective HBA.
>
> Instead of
>
> HPT374
> ide4
> ide5
> HPT374
> ide6
> ide7
>
> It has to evlolve to
>
> HPT374
> ide4p
> ide4s
> ide5p
> ide5s
>
> This means extened minor on the second half of each major must be created.
> There is not enough sane bandwith in the driver, nor would anybody take
> such an exotic solution.
>
> Sorry,
>
> Andre Hedrick
> LAD Storage Consulting Group
>
prev parent reply other threads:[~2002-07-25 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 11:49 Mike Insch
2002-07-25 12:25 ` Andre Hedrick
2002-07-25 13:10 ` Mike Insch [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=200207251410.57227.vofka@hotpop.com \
--to=vofka@hotpop.com \
--cc=andre@linux-ide.org \
--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
all inboxes | Powered by JetHome®