From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Kittipon Meesompop
<kmeesomp-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] libmlx5: add support for the s390x platform
Date: Wed, 13 Sep 2017 12:19:30 -0600 [thread overview]
Message-ID: <20170913181930.GC1536@obsidianresearch.com> (raw)
In-Reply-To: <0c2d33a4-c9b1-a20d-b113-502288eae525-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
On Wed, Sep 13, 2017 at 02:55:01PM +0200, Kittipon Meesompop wrote:
> Thanks for your info; we should have listened better to linux-rdma. That
> means my sent libmlx5 patch is not needed anymore. I now have run dapltest
> with your rdma-core provided libraries libmlx4.so,1.0.15 and
> libmlx5.so.1.2.15 on an IBM internally built driver for s390.
> libmlx5 results with and without vlan interfaces look good, libmlx4 results
> look good for non-vlan interfaces. Analysis of the libmlx4 failure for
> vlan-interfaces is ongoing; it might just be a driver issue.
Okay, thanks! That is good to hear.
Jason
--
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:[~2017-09-13 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 13:36 [PATCH] libmlx5: add support for the s390x platform Kittipon Meesompop
[not found] ` <20170906133620.58716-1-kmeesomp-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-09-06 14:15 ` Leon Romanovsky
[not found] ` <20170906141500.GJ18084-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-06 15:22 ` Jason Gunthorpe
[not found] ` <20170906152208.GB6262-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-13 12:55 ` Kittipon Meesompop
[not found] ` <0c2d33a4-c9b1-a20d-b113-502288eae525-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-09-13 18:19 ` Jason Gunthorpe [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=20170913181930.GC1536@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=kmeesomp-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 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).