mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Jacob <mjacob@feral.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	christophe barbi <christophe.barbe@lineo.fr>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Qlogic Fiber Channel
Date: Fri, 29 Jun 2001 13:51:19 -0700 (PDT)	[thread overview]
Message-ID: <20010629134917.X13977-100000@wonky.feral.com> (raw)
In-Reply-To: <15164.59568.527480.216539@pizda.ninka.net>



On Fri, 29 Jun 2001, David S. Miller wrote:

>
> Alan Cox writes:
>  > > =46rom my point of view, this driver is sadly broken. The fun part is t=
>  > > hat
>  > > the qlogic driver is certainly based on this one too (look at the code,=
>  > >  the
>  > > drivers differs not so much).=20
>  >
>  > And if the other one is stable someone should spend the time merging the
>  > two.
>
> Actually, I think "sadly broken" depends upon your situation.
> I've been using the driver just fine on my systems here, even
> during cerberus stress testing.  So it is working perfectly fine
> for some people.

That's actually the story of Fibre Channel.

What is cerberus testing?

Try the following: try issuing a LIP every 180 seconds for 24 hours
during load with auditted pattern checkers (whether local loop or fabric
topologies). If you (and, haha, your fabric switches) survive that
without losing data or disks, then we'll begin to talk about 'fine'.

-matt



  reply	other threads:[~2001-06-29 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29 10:52 Mike Black
2001-06-29 13:19 ` christophe barbé
2001-06-29 15:09   ` Alan Cox
2001-06-29 15:36     ` christophe barbé
2001-06-29 15:38       ` Alan Cox
2001-06-29 15:48       ` Matthew Jacob
2001-06-29 20:44   ` David S. Miller
2001-06-29 20:51     ` Matthew Jacob [this message]
2001-06-29 20:54     ` David S. Miller
2001-06-29 15:17 conway, heather

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=20010629134917.X13977-100000@wonky.feral.com \
    --to=mjacob@feral.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=christophe.barbe@lineo.fr \
    --cc=davem@redhat.com \
    --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®