From: "Nicholas A. Bellinger" <nick@pyxtechnologies.com>
To: James Bottomley <James.Bottomley@SteelEye.com>,
Christoph Hellwig <hch@lst.de>, Mike Christie <mikenc@us.ibm.com>,
Andre Hedrick <andre@pyxtechnologies.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: [ANNOUNCE] iSCSI Initiator Core Stack v1.6.1.20
Date: Wed, 23 Feb 2005 11:45:35 -0800 [thread overview]
Message-ID: <1109187935.15154.164.camel@haakon> (raw)
The following is the first public release of the PyX Technologies iSCSI
Initiator Core Stack v1.6.1.20 for Linux 2.6.11-rc4. This is a full
featured iSCSI Initiator stack that is capable of mulitplexing coast to
coast across multiple independant backbone providers using various
network transports _TODAY_. This is the first release of the core stack
and assoicated userspace tools, the accompanying authentication daemon
will be released shortly.
There is ongoing work in taking advantage of the very latest 2.6
kernel's SCSI functionality, namely drivers/scsi/scsi_transport_iscsi.c.
The near term work for the iSCSI Initiator Core Stack includes taking
advantage of these new abstractions in scsi_transport_scsi.c in a manner
to reduce code duplication across the iSCSI Initiator Core Stack and
linux-sfnet implementations. An initial patch to scsi_transport_scsi.c
will be provided in order stay in line with the iSCSI Session/Connection
contexts definied in section 12 of RFC 3720. Additionally this patch
will add initial support for iSCSI Extentions for RDMA (iSER)
optertional keys in order to help facilitate development of iSCSI with
RDMA Capable Protocols (RCP) in the Linux 2.6 environment.
The patch against 2.6.11-rc4 in diff format can be found at:
http://www.kernel.org/pub/linux/kernel/people/nab/iscsi-initiator-core
The assoicated userspace tools and documentation:
http://www.kernel.org/pub/linux/utils/storage/iscsi
For more information on the Internet Small Computer Systems Interface
(iSCSI) standard, please see:
http://www.ietf.org/rfc/rfc3720.txt
The iSCSI Initiator Core Stack contains, but is not limited to the
following features:
1) Full support for Internet Small Computer Systems Interface (iSCSI)
state machine as defined by RFC 3720.
2) Full support for ErrorRecoveryLevel=0 feature set as defined for RFC
3720.
3) Full support for Multiple Connections per Session that can be brought
up and down on the fly.
4) Full support for DataPDUInOrder=No, DataSequenceInOrder=No,
MaxOutstandingR2T>1.
5) Full support for Sync and Steering using Fixed Interval Markers. (See
RFC 3720 Appendix A)
6) Full support for TCP and SCTP network transports.
7) Robust set of iSCSI Channel management options for iSCSI SAN
Administrators.
8) Tested on UP/SMP 32/64-bit Big/Little Endian architectures.
--
Nicholas A. Bellinger <nick@pyxtechnologies.com>
Chief Architect, PyX Technologies, Inc.
next reply other threads:[~2005-02-23 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 19:45 Nicholas A. Bellinger [this message]
2005-02-23 21:03 ` [ANNOUNCE] iSCSI Initiator Core Stack v1.6.1.20 Jeff Garzik
2005-02-23 23:11 ` Nicholas A. Bellinger
2005-02-24 20:51 ` AJ Lewis
2005-02-25 7:50 ` Nicholas A. Bellinger
2005-02-25 15:18 ` AJ Lewis
2005-02-25 19:32 ` Nicholas A. Bellinger
2005-02-27 18:46 ` Dave Wysochanski
2005-02-28 8:22 ` Andre Hedrick
2005-02-28 13:41 ` Dave Wysochanski
2005-02-28 15:16 ` AJ Lewis
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=1109187935.15154.164.camel@haakon \
--to=nick@pyxtechnologies.com \
--cc=James.Bottomley@SteelEye.com \
--cc=andre@pyxtechnologies.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mikenc@us.ibm.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