From: "christophe barbé" <christophe.barbe@lineo.fr>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Qlogic Fiber Channel
Date: Fri, 29 Jun 2001 17:36:31 +0200 [thread overview]
Message-ID: <20010629173631.A15608@pc8.lineo.fr> (raw)
In-Reply-To: <20010629151910.C27847@pc8.lineo.fr> <E15Fzu8-0000SK-00@the-village.bc.nu>
In-Reply-To: <E15Fzu8-0000SK-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on ven, jun 29, 2001 at 17:09:56 +0200
Le ven, 29 jun 2001 17:09:56, Alan Cox a écrit :
> > From my point of view, this driver is sadly broken. The fun part is
that
> > the qlogic driver is certainly based on this one too (look at the code,
> > the drivers differs not so much).
>
> And if the other one is stable someone should spend the time merging the
> two.
That what I would like to try but It seems impossible without an
IP-enhanced firmware. I could try with the old firmware but I believe that
the new code from QLogic use some features that are only in recent
firmware.
>
> > IMHO the qlogicfc driver should be removed from the kernel tree and
> > perhaps replaced by the last qlogic one. We then lost the IP support
> > but this is a broken support.
>
> For 2.5 that may wellk make sense. Personally I'd prefer someone worked
> out
> why the qlogicfc driver behaves as it does. It sounds like two small bugs
> nothing more
>
> 1. That the FC event code wasnt updated from 2.2 so now runs
> with IRQ's off when it didnt expect it
>
> 2. That someone has a slight glitch in the queue handling.
This driver is already buggy under kernel 2.2. This driver is a well known
source of problems in the GFS mailing lists.
I believe that the better thing to do is to use the qlogic driver. If we
manage to get a recent IP-enhanced firmware we could rewrite the missing IP
code. Half of the job is already done in the source of this driver.
I didn't manage to reach the good person from qlogic. Perhaps someone would
have better results.
Christophe
--
Christophe Barbé
Software Engineer - christophe.barbe@lineo.fr
Lineo France - Lineo High Availability Group
42-46, rue Médéric - 92110 Clichy - France
phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01
http://www.lineo.com
next prev parent reply other threads:[~2001-06-29 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 10:52 Qlogic Fiber Channel Mike Black
2001-06-29 13:19 ` christophe barbé
2001-06-29 15:09 ` Alan Cox
2001-06-29 15:36 ` christophe barbé [this message]
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
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=20010629173631.A15608@pc8.lineo.fr \
--to=christophe.barbe@lineo.fr \
--cc=alan@lxorguk.ukuu.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;
as well as URLs for NNTP newsgroup(s).