From: Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] mlx5: Fix missing device local_dma_lkey
Date: Mon, 20 Jul 2015 20:09:57 +0300 [thread overview]
Message-ID: <55AD2B65.4090006@mellanox.com> (raw)
In-Reply-To: <3095C235-676F-4A99-A27C-F2F332D9921F-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On 7/20/2015 8:08 PM, Chuck Lever wrote:
>
> On Jul 20, 2015, at 12:54 PM, Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org> wrote:
>
>> The mlx5 driver exposes device capability IB_DEVICE_LOCAL_DMA_LKEY
>> but does not set the the device local_dma_lkey. This breaks
>> rpcrdma drivers.
>>
>> Query and set this lkey when creating the device resources.
>
> Wow. This suggests no-one has been testing NFS/RDMA with mlx5? I
> know I’m not (yet). Anyway, this makes sense.
That's what I was wandering about.
I just turned it on and it blew up... gracefully though :)
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-20 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 16:54 [PATCH] mlx5: Fix missing device local_dma_lkey Sagi Grimberg
[not found] ` <1437411276-22731-1-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-07-20 17:08 ` Chuck Lever
[not found] ` <3095C235-676F-4A99-A27C-F2F332D9921F-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-07-20 17:09 ` Sagi Grimberg [this message]
[not found] ` <55AD2B65.4090006-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-07-20 19:52 ` Jason Gunthorpe
2015-07-28 15:09 ` Doug Ledford
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=55AD2B65.4090006@mellanox.com \
--to=sagig-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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.