linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: "ira.weiny" <ira.weiny@intel.com>,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Haggai Eran <haggaie@mellanox.com>,
	linux-rdma@vger.kernel.org, Amir Vadai <amirv@mellanox.com>,
	Bart Van Assche <bart.vanassche@sandisk.com>,
	Chien Yen <chien.yen@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	Dominique Martinet <dominique.martinet@cea.fr>,
	Eli Cohen <eli@mellanox.com>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Ido Shamay <idos@mellanox.com>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Or Gerlitz <ogerlitz@mellanox.com>, Roi Dayan <roid@mellanox.com>,
	Ron Minnich <rminnich@sandia.gov>,
	Sagi Grimberg <sagig@mellanox.com>,
	Simon Derr <simon.derr@bull.net>,
	Tom Tucker <tom@opengridcomputing.com>,
	rds-devel@oss.oracle.com, target-devel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH v3 01/12] IB/core: Guarantee that a local_dma_lkey is available
Date: Fri, 14 Aug 2015 20:54:55 -0400	[thread overview]
Message-ID: <55CE8DDF.4020403@redhat.com> (raw)
In-Reply-To: <20150804233520.GA22313@phlsvsds.ph.intel.com>

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

On 08/04/2015 07:35 PM, ira.weiny wrote:
> On Tue, Aug 04, 2015 at 04:21:30PM -0600, Jason Gunthorpe wrote:
>> Every single ULP requires a local_dma_lkey to do anything with
>> a QP, so let us ensure one exists for every PD created.
>>
>> If the driver can supply a global local_dma_lkey then use that, otherwise
>> ask the driver to create a local use all physical memory MR associated
>> with the new PD.
>>
>> Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
>> Reviewed-by: Sagi Grimberg <sagig@dev.mellanox.co.il>
>> Acked-by: Christoph Hellwig <hch@infradead.org>
>> Reviewed-by: Steve Wise <swise@opengridcomputing.com>
> 
> I hit this bug as well.
> 
> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> Tested-by: Ira Weiny <ira.weiny@intel.com>

I've pulled the v2 of this patch and replaced it with this one.  Thanks.


-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: 0E572FDD



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

      reply	other threads:[~2015-08-15  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 22:21 [PATCH v3 01/12] IB/core: Guarantee that a local_dma_lkey is available Jason Gunthorpe
2015-08-04 23:35 ` ira.weiny
2015-08-15  0:54   ` Doug Ledford [this message]

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=55CE8DDF.4020403@redhat.com \
    --to=dledford@redhat.com \
    --cc=amirv@mellanox.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=chien.yen@oracle.com \
    --cc=dominique.martinet@cea.fr \
    --cc=eli@mellanox.com \
    --cc=ericvh@gmail.com \
    --cc=haggaie@mellanox.com \
    --cc=hch@infradead.org \
    --cc=idos@mellanox.com \
    --cc=ira.weiny@intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=ogerlitz@mellanox.com \
    --cc=rds-devel@oss.oracle.com \
    --cc=rminnich@sandia.gov \
    --cc=roid@mellanox.com \
    --cc=sagig@mellanox.com \
    --cc=simon.derr@bull.net \
    --cc=target-devel@vger.kernel.org \
    --cc=tom@opengridcomputing.com \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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).