public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: dledford@redhat.com, bart.vanassche@sandisk.com
Cc: swise@opengridcomputing.com, sagig@mellanox.com,
	linux-rdma@vger.kernel.org, target-devel@vger.kernel.org
Subject: generic RDMA READ/WRITE API V5
Date: Fri, 11 Mar 2016 19:53:10 +0100	[thread overview]
Message-ID: <1457722399-25811-1-git-send-email-hch@lst.de> (raw)

This series contains patches that implement a first version of a generic
API to handle RDMA READ/WRITE operations as commonly used on the target
(or server) side for storage protocols.

This has been developed for the upcoming NVMe over Fabrics target, and
extensively teѕted as part of that, although this upstream version has
additional updates over the one we're currently using.

It hides details such as the use of MRs for iWarp devices, and will allow
looking at other HCA specifics easily in the future.

This series contains a conversion of the SRP target, and the git tree
below also has a RFC conversion of the iSER target (a little hacky
due to the signature MR support which I can't test)

I think it's basically ready to merge now.

I also have a git tree available at:

	git://git.infradead.org/users/hch/rdma.git rdma-rw-api

Gitweb:

	http://git.infradead.org/users/hch/rdma.git/shortlog/refs/heads/rdma-rw-api

These two also include the RFC iSER target conversion.

Changes since V4:
 - fix SG iteration in rdma_rw_init_mr_wrs
 - address various misc review feedback items from Bart and Leon

Changes since V3:
 - really fold the list_del in mr_pool_get into the right patch

Changes since V2:
 - fold the list_del in mr_pool_get into the right patch
 - clamp the max FR page size length
 - minor srpt style fix
 - spelling fixes
 - renamed rdma_has_read_invalidate to rdma_cap_read_inv

Changes since V1:
 - fixed offset handling in ib_sg_to_pages
 - uses proper SG iterators to handle larger than PAGE_SIZE segments
 - adjusted parameters for some functions to reduce size of the context
 - SRP target support

             reply	other threads:[~2016-03-11 18:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 18:53 Christoph Hellwig [this message]
2016-03-11 18:53 ` [PATCH v5 1/9] IB/cma: pass the port number to ib_create_qp Christoph Hellwig
2016-03-11 18:53 ` [PATCH v5 2/9] IB/core: allow passing mapping an offset into the SG in ib_map_mr_sg Christoph Hellwig
2016-03-11 18:53 ` [PATCH v5 3/9] IB/core: add a helper to check for READ WITH INVALIDATE support Christoph Hellwig
2016-03-11 18:53 ` [PATCH v5 4/9] IB/core: refactor ib_create_qp Christoph Hellwig
2016-03-11 18:53 ` [PATCH v5 5/9] IB/core: add a simple MR pool Christoph Hellwig
2016-03-11 18:53 ` [PATCH v5 6/9] IB/core: add a need_inval flag to struct ib_mr Christoph Hellwig
2016-03-11 18:53 ` [PATCH v5 7/9] IB/core: generic RDMA READ/WRITE API Christoph Hellwig
     [not found] ` <1457722399-25811-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-03-11 18:53   ` [PATCH v5 8/9] target: enhance and export target_alloc_sgl/target_free_sgl Christoph Hellwig
2016-03-11 18:53   ` [PATCH v5 9/9] IB/srpt: convert to the generic RDMA READ/WRITE API 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=1457722399-25811-1-git-send-email-hch@lst.de \
    --to=hch@lst.de \
    --cc=bart.vanassche@sandisk.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sagig@mellanox.com \
    --cc=swise@opengridcomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox