From: Alex Aizman <itn780@yahoo.com>
To: netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] Linux-iSCSI High-Performance Initiator
Date: Tue, 19 Apr 2005 07:34:54 -0700 [thread overview]
Message-ID: <4265170E.5040102@yahoo.com> (raw)
Input is needed...
Two weeks ago the combined linux-iscsi and open-iscsi teams posted
on lkml and linux-scsi "Linux-iSCSI High-Performance Initiator" -
announcement and a set of patches.
Here's the original announcement and the submission, respectively:
http://marc.theaimsgroup.com/?l=linux-kernel&m=111327337005048&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=111328256211837&w=2
The entire iSCSI Initiator's data path over TCP consists of 2 files:
http://www.open-iscsi.org/src/iscsi_tcp.c
http://www.open-iscsi.org/src/iscsi_tcp.h
(The first file is 73K, I sent yesterday - seems it didn't make it).
It'd be great to get this code reviewed from the networking perspective.
Thanks!
Alex
next reply other threads:[~2005-04-19 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 14:34 Alex Aizman [this message]
2005-04-19 14:39 ` [ANNOUNCE] Linux-iSCSI High-Performance Initiator Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2005-05-05 4:31 Alex Aizman
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=4265170E.5040102@yahoo.com \
--to=itn780@yahoo.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).