From: Or Gerlitz <ogerlitz@voltaire.com>
To: James.Bottomley@SteelEye.com, hch@lst.de, linux-scsi@vger.kernel.org
Cc: michaelc@cs.wisc.edu
Subject: Re: [PATCH] iscsi transport endpoint calls
Date: Mon, 24 Apr 2006 17:54:38 +0300 [thread overview]
Message-ID: <444CE6AE.8020502@voltaire.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0604111646040.18200-100000@zuben>
Or Gerlitz wrote:
> This patch allows for iscsi transport to have its connection
> being established and disconnected from the kernel.
>
> The patch is the sixth iscsi update to 2.6.18 and is needed by iser,
> it is relative to the five iscsi patches sent by Mike Christie.
>
> Doing this is a must for iSER and some of the iscsi offloads but on the
> other hand not needed for TCP where a socket (fd) is connected in user space
> and then sent down to the kernel where struct sock is retrieved from the fd.
>
> The iscsi user space implementation was enhanced to have a user space
> transport where TCP is doing things directly from user space and iSER
> is using the extension to the iscsi u/k IPC ABI to do things in the kernel.
>
> Acked-by: Mike Christie <michaelc@cs.wisc.edu>
> Signed-off-by: Or Gerlitz <ogerlitz@voltaire.com>
James, Christoph:
As the iscsi patches sent by Mike Christie were accepted and merged into
the scsi-misc git tree, this patch is the remaining iscsi related piece
on which iser is dependent and is not yet accepted for upstream push.
We really need your feedback on the patch, which allowed us to remove
the pseudo socket from iser (Christoph is aware to the details).
Once the patch is accepted, Roland will open a branch for iser upstream
push on the his infiniband git tree and pull the iscsi updates into it,
so the tree compiles.
Or.
next prev parent reply other threads:[~2006-04-24 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 13:45 [RFC] iSER (iSCSI Extensions for RDMA) Or Gerlitz
2006-04-11 13:47 ` [PATCH] iscsi transport endpoint calls Or Gerlitz
2006-04-11 13:48 ` [PATCH 1/6] [RFC] iSER's Makefile and Kconfig Or Gerlitz
2006-04-11 13:49 ` [PATCH 2/6] [RFC] iscsi_iser header file Or Gerlitz
2006-04-11 13:49 ` [PATCH 3/6] [RFC] open iscsi iser transport provider code Or Gerlitz
2006-04-11 13:50 ` [PATCH 4/6] [RFC] iser initiator Or Gerlitz
2006-04-11 13:51 ` [PATCH 5/6] [RFC] iser cma and verbs interaction Or Gerlitz
2006-04-11 13:51 ` [PATCH 6/6] [RFC] iser handling of memory for RDMA Or Gerlitz
2006-04-24 14:54 ` Or Gerlitz [this message]
2006-04-24 17:01 ` [PATCH] iscsi transport endpoint calls Mike Christie
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=444CE6AE.8020502@voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.