From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Sagi Grimberg
<sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Sebastian Riemer
<sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>,
Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: IB/srp: merge fixes from MLNX_OFED
Date: Tue, 18 Feb 2014 18:42:51 +0100 [thread overview]
Message-ID: <53039B9B.2080907@acm.org> (raw)
In-Reply-To: <53039779.3080507-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 02/18/14 18:25, Sagi Grimberg wrote:
> Regarding the FMR unmap crash, I experienced it when running our
> distro-backported MLNX_OFED
> and hadn't got a chance to see if it reproduces in upstream yet. Thanks
> for confirming this reproduces here as well.
> Bart, Are you familiar with this issue? it should reproduce over mlx5
> driver or SRIOV (where FMRs are not supported).
The only issue I am aware of with regard to FMR and mlx4 was specific to
a single vendor kernel in which the FMR code had been modified. mlx4 +
FMR works fine AFAIK with RHEL, SLES and with upstream kernels.
Unfortunately I have not yet had the chance to give the mlx5 driver a try.
Bart.
--
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
prev parent reply other threads:[~2014-02-18 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 16:47 IB/srp: merge fixes from MLNX_OFED Sebastian Riemer
[not found] ` <53038E93.7050706-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2014-02-18 17:05 ` Bart Van Assche
[not found] ` <530392D9.1010900-HInyCGIudOg@public.gmane.org>
2014-02-18 17:25 ` Sagi Grimberg
[not found] ` <53039779.3080507-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2014-02-18 17:42 ` Bart Van Assche [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=53039B9B.2080907@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@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.