From: Steve Wise <swise@opengridcomputing.com>
To: dledford@redhat.com
Cc: roid@mellanox.com, linux-rdma@vger.kernel.org,
sagig@mellanox.com, infinipath@intel.com,
target-devel@vger.kernel.org, eli@mellanox.com,
ogerlitz@mellanox.com
Subject: [PATCH V3 0/4] iSER support for iWARP
Date: Wed, 01 Jul 2015 11:30:37 -0500 [thread overview]
Message-ID: <20150701162936.6501.45512.stgit@build.ogc.int> (raw)
The following series implements support for iWARP transports in the iSER
initiator and target. This is based on Doug's k.o/for-4.2 branch.
I've tested this on cxgb4 and mlx4 hardware.
Changes since V2:
The transport independent work is removed from this series and will
be submitted in a subsequent series. This V3 series now enables iWARP
using existing core services.
Changes since V1:
Introduce and use transport-independent RDMA core services for allocating
DMA MRs and computing fast register access flags.
Correctly set the device max_sge_rd capability in several rdma device
drivers.
isert: use device capability max_sge_rd for the read sge depth.
isert: change max_sge to max_write_sge in struct isert_conn.
---
Sagi Grimberg (1):
mlx4, mlx5, mthca: Expose max_sge_rd correctly
Steve Wise (3):
ipath,qib: Expose max_sge_rd correctly
RDMA/iser: limit sg tablesize to device fastreg max depth
RDMA/isert: Support iWARP transport
drivers/infiniband/hw/ipath/ipath_verbs.c | 1
drivers/infiniband/hw/mlx4/main.c | 1
drivers/infiniband/hw/mlx5/main.c | 1
drivers/infiniband/hw/mthca/mthca_provider.c | 1
drivers/infiniband/hw/qib/qib_verbs.c | 1
drivers/infiniband/ulp/iser/iscsi_iser.c | 7 +++
drivers/infiniband/ulp/isert/ib_isert.c | 54 ++++++++++++++++++++++----
drivers/infiniband/ulp/isert/ib_isert.h | 3 +
8 files changed, 59 insertions(+), 10 deletions(-)
--
Steve.
next reply other threads:[~2015-07-01 16:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 16:30 Steve Wise [this message]
2015-07-01 16:30 ` [PATCH V3 1/4] mlx4, mlx5, mthca: Expose max_sge_rd correctly Steve Wise
[not found] ` <20150701162936.6501.45512.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2015-07-01 16:30 ` [PATCH V3 2/4] ipath,qib: " Steve Wise
2015-07-01 16:30 ` [PATCH V3 4/4] RDMA/isert: Support iWARP transport Steve Wise
[not found] ` <20150701163058.6501.39171.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2015-07-01 17:16 ` Sagi Grimberg
2015-07-01 20:33 ` Or Gerlitz
2015-07-01 20:53 ` Steve Wise
2015-07-01 21:03 ` Or Gerlitz
2015-07-02 6:28 ` Sagi Grimberg
[not found] ` <5594DA1E.7040604-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-07-02 13:17 ` Steve Wise
2015-07-02 16:39 ` Jason Gunthorpe
[not found] ` <20150702163937.GB4642-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-07-04 10:51 ` Sagi Grimberg
2015-07-01 16:30 ` [PATCH V3 3/4] RDMA/iser: limit sg tablesize to device fastreg max depth Steve Wise
[not found] ` <20150701163052.6501.27775.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2015-07-01 17:07 ` Sagi Grimberg
[not found] ` <55941E6F.5080208-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-07-01 18:11 ` Steve Wise
2015-07-01 20:27 ` Or Gerlitz
2015-07-01 20:41 ` Steve Wise
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=20150701162936.6501.45512.stgit@build.ogc.int \
--to=swise@opengridcomputing.com \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=infinipath@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roid@mellanox.com \
--cc=sagig@mellanox.com \
--cc=target-devel@vger.kernel.org \
/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.