All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-rdma@vger.kernel.org, swise@opengridcomputing.com,
	sagig@mellanox.com, target-devel@vger.kernel.org,
	Steve Wise <swise@chelsio.com>
Subject: Re: [PATCH 06/13] IB/core: add a need_inval flag to struct ib_mr
Date: Sun, 28 Feb 2016 17:05:45 +0100	[thread overview]
Message-ID: <20160228160545.GC23421@lst.de> (raw)
In-Reply-To: <56D30DE2.9080007@dev.mellanox.co.il>

On Sun, Feb 28, 2016 at 05:10:26PM +0200, Sagi Grimberg wrote:
>> This is the first step toward moving MR invalidation decisions
>> to the core.  It will be needed by the upcoming RW API.
>
> This makes sense even before the rdma rw stuff. We can
> add this bit and get rid of the iser flagging (and when
> nfs/srp will support remote invalidate they will use it too)

If someone else has a use for it ASAP feel free to send it along
with that.  The R/W code currently is my priority project because
the NVMe target driver will need it.  Once that and a few other
urgent items are off my plate I'll happily help out with various
cleanups on the client side MR API again.

  reply	other threads:[~2016-02-28 16:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 18:10 RFC: a first draft of a generic RDMA READ/WRITE API Christoph Hellwig
2016-02-27 18:10 ` [PATCH 04/13] IB/core: refactor ib_create_qp Christoph Hellwig
2016-02-27 18:10 ` [PATCH 06/13] IB/core: add a need_inval flag to struct ib_mr Christoph Hellwig
2016-02-28 15:10   ` Sagi Grimberg
2016-02-28 16:05     ` Christoph Hellwig [this message]
     [not found] ` <1456596631-19418-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-02-27 18:10   ` [PATCH 01/13] IB/cma: pass the port number to ib_create_qp Christoph Hellwig
2016-02-27 18:10   ` [PATCH 02/13] IB/core: allow passing mapping an offset into the SG in ib_map_mr_sg Christoph Hellwig
     [not found]     ` <1456596631-19418-3-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-02-28 14:57       ` Sagi Grimberg
2016-02-28 16:20         ` Christoph Hellwig
2016-02-28 17:50           ` Sagi Grimberg
     [not found]             ` <56D33356.1020707-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-02-29 22:22               ` Steve Wise
2016-02-29 11:15         ` Christoph Hellwig
     [not found]           ` <20160229111557.GA11499-jcswGhMUV9g@public.gmane.org>
2016-02-29 11:35             ` Sagi Grimberg
2016-02-29 11:56               ` Christoph Hellwig
2016-02-29 12:08                 ` Sagi Grimberg
2016-02-27 18:10   ` [PATCH 03/13] IB/core: add a helper to check for READ WITH INVALIDATE support Christoph Hellwig
2016-02-27 18:10   ` [PATCH 05/13] IB/core: add a simple MR pool Christoph Hellwig
2016-03-02  2:48     ` Parav Pandit
2016-03-02  9:15       ` Christoph Hellwig
2016-03-02 15:22         ` Bart Van Assche
     [not found]           ` <56D70543.1000506-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-03-03  8:30             ` Christoph Hellwig
2016-02-27 18:10   ` [PATCH 07/13] IB/core: generic RDMA READ/WRITE API Christoph Hellwig
2016-02-28 15:05     ` Sagi Grimberg
2016-02-27 18:10   ` [PATCH 08/13] IB/isert: properly type the login buffer Christoph Hellwig
2016-02-27 18:10   ` [PATCH 09/13] IB/isert: convert to new CQ API Christoph Hellwig
2016-02-27 18:10   ` [PATCH 10/13] IB/isert: kill struct isert_rdma_wr Christoph Hellwig
2016-02-27 18:10   ` [PATCH 12/13] IB/core: add a MR pool for signature MRs Christoph Hellwig
2016-02-27 18:10 ` [PATCH 11/13] IB/isert: the kill ->isert_cmd back pointer in the struct iser_tx_desc Christoph Hellwig
2016-02-27 18:10 ` [PATCH 13/13] IB/isert: RW API WIP Christoph Hellwig
2016-02-28 13:57   ` Sagi Grimberg
2016-02-28 16:04     ` 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=20160228160545.GC23421@lst.de \
    --to=hch@lst.de \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sagig@dev.mellanox.co.il \
    --cc=sagig@mellanox.com \
    --cc=swise@chelsio.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 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.