From: Dmitry Yusupov <dmitry_yus@yahoo.com>
To: Duane Grigsby <duane.grigsby@qlogic.com>
Cc: Christoph Hellwig <hch@lst.de>,
open-iscsi@googlegroups.com,
linux-iscsi development team
<linux-iscsi-devel@lists.sourceforge.net>,
linux-scsi@vger.kernel.org
Subject: RE: 5.x branch mainline kernel push in two weeks?
Date: Wed, 20 Apr 2005 11:50:08 -0700 [thread overview]
Message-ID: <1114023008.14522.30.camel@beastie> (raw)
In-Reply-To: <41EBA11203419D4CA8EB4C6140D8B4010295B3C5@AVEXCH01.qlogic.org>
On Wed, 2005-04-20 at 11:29 -0700, Duane Grigsby wrote:
> No, that's not true; we are TOTALLY committed to getting all of our
> drivers in the upstream kernel. I have been working on the ISCSI driver
> cleanup to the level of our Fibre Channel driver as Andrew has done. I'm
> making it conform to the current linux-scsi API, ISCSI transport, and
> stripping out all of the failover baggage. My goal is the have something
> upstream in 2 - 3 weeks, if not before.
But don't you think it is better to have integrated solution for all
iSCSI transports including QLogic's HBA and have unified user-space set
of tools? How about collaborate on this issue and come up with somewhat
generic which will fit with ongoing efforts we have today:
1) iSCSI/TCP
2) your QLogic's HBA
3) iSER/IB
I think those three projects combined could come up with generic iSCSI
solution(including user-space tools and API) which will really fit for
everyone else on the planet.
It would be really nice if you would participate in ongoing interface
discussion on next mailing lists:
1) linux-iscsi-devel@lists.sourceforge.net
2) open-iscsi@googlegroups.com
3) iscsitarget-devel@lists.sourceforge.net
Thanks!
> -----Original Message-----
> From: linux-scsi-owner@vger.kernel.org
> [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Christoph Hellwig
> Sent: Wednesday, April 20, 2005 1:49 AM
> To: open-iscsi@googlegroups.com
> Cc: linux-iscsi development team; linux-scsi@vger.kernel.org
> Subject: Re: 5.x branch mainline kernel push in two weeks?
>
> On Wed, Apr 20, 2005 at 01:29:11AM -0700, Mike Christie wrote:
> > Are you going to try and push someone like qla4010 which has a similar
>
> > interface to qla2xxx (it uses the msg box interface) to use the
> netlink
> > interface? With a lot of the iscsi stuff masked away it seems a little
>
> > difficult to go the extent open-iscsi did?
>
> I'm not sure we should care too much about the qla4xxx driver. It's
> never been posted to linux-scsi, and the driver they pushed to SuSE
> ignores everything we've said about scsi low-level drivers. It looks
> like the iSCSI part of Qlogic simply doesn't care about Linux (that is
> upstream, not the major forks)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-04-20 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 18:29 5.x branch mainline kernel push in two weeks? Duane Grigsby
2005-04-20 18:31 ` Christoph Hellwig
2005-04-20 18:50 ` Dmitry Yusupov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-20 20:37 Duane Grigsby
2005-04-20 20:32 Duane Grigsby
[not found] <1113844382.13939.230.camel@beastie>
[not found] ` <20050418181352.GA2983@lst.de>
[not found] ` <426612D7.3010701@cs.wisc.edu>
2005-04-20 8:49 ` Christoph Hellwig
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=1114023008.14522.30.camel@beastie \
--to=dmitry_yus@yahoo.com \
--cc=duane.grigsby@qlogic.com \
--cc=hch@lst.de \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=open-iscsi@googlegroups.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