From: Mike Christie <mikenc@us.ibm.com>
To: naveenb@cisco.com
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: Request for review of Linux iSCSI driver version 4.0.0.3
Date: Mon, 29 Dec 2003 13:23:18 -0800 [thread overview]
Message-ID: <3FF09B46.5070902@us.ibm.com> (raw)
In-Reply-To: <03122920412702.20911@naveenb-lnx.cisco.com>
>> - as Mike Christie you're doing multipathing in your driver. We don't
>> want vendor-specific multipathing code in scsi-drivers but instead
>> encurage using md or dm multipathing.
>>
>
>
> linux-iscsi driver 4.0.0.2 is not doing multipathing instead it provides
> infrastructure to do multipathing and encourages other applications/drivers
> like md to do multipathing.
>
>
I think Christoph may have meant to write "Failover" above.
mike
next prev parent reply other threads:[~2003-12-29 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 13:40 Request for review of Linux iSCSI driver version 4.0.0.3 Naveen Burmi
2003-12-28 20:25 ` Christoph Hellwig
2003-12-29 15:11 ` Naveen Burmi
2003-12-29 21:23 ` Mike Christie [this message]
2003-12-31 11:07 ` Naveen Burmi
2003-12-31 21:22 ` Andre Hedrick
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=3FF09B46.5070902@us.ibm.com \
--to=mikenc@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=naveenb@cisco.com \
/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