From: Simon Kelley <simon@thekelleys.org.uk>
To: linux-scsi@vger.kernel.org
Subject: Is there a grand plan for FC failover?
Date: Mon, 26 Jan 2004 14:18:15 +0000 [thread overview]
Message-ID: <401521A7.5030808@thekelleys.org.uk> (raw)
I see that 2.6.x kernels now have the qla2xxx driver in the mainline,
but without the failover code.
What is the reason for that? Is there a plan provide failover facilities
at a higher level which will be usable with all suitable low-level
drivers and hardware?
I'm very much in favour of using drivers which are developed in the
kernel mainline but I have an application which needs failover so I
might be forced back to the qlogic-distributed code.
Cheers,
Simon.
next reply other threads:[~2004-01-26 14:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 14:18 Simon Kelley [this message]
2004-01-26 15:37 ` Is there a grand plan for FC failover? James Bottomley
2004-01-28 15:02 ` Philip R. Auld
2004-01-28 16:57 ` James Bottomley
2004-01-28 18:00 ` Philip R. Auld
2004-01-28 20:47 ` Patrick Mansfield
2004-01-28 22:14 ` James Bottomley
2004-01-29 0:55 ` Patrick Mansfield
2004-01-30 19:48 ` [dm-devel] " Joe Thornber
2004-01-31 9:30 ` Jens Axboe
2004-01-31 16:59 ` Philip R. Auld
2004-01-31 17:42 ` Jens Axboe
2004-02-12 15:17 ` Philip R. Auld
2004-02-12 15:28 ` Arjan van de Ven
2004-02-12 16:03 ` Philip R. Auld
2004-01-28 22:37 ` Mike Christie
2004-01-29 15:24 ` Philip R. Auld
2004-01-29 16:00 ` James Bottomley
2004-01-29 23:25 ` Mike Christie
-- strict thread matches above, loose matches on Subject: below --
2004-01-28 21:02 Smart, James
2004-01-28 22:16 ` James Bottomley
2004-01-29 14:49 ` Philip R. Auld
2004-01-29 15:05 ` James Bottomley
2004-01-29 17:35 Smart, James
2004-01-29 18:31 ` Mike Anderson
2004-01-29 18:31 ` James Bottomley
2004-01-29 18:41 Smart, James
2004-01-29 19:37 Smart, James
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=401521A7.5030808@thekelleys.org.uk \
--to=simon@thekelleys.org.uk \
--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