From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: Linux RDMA list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ewg <ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>
Subject: Re: broken support for UC in rdma_cm
Date: Mon, 15 Mar 2010 15:45:27 +0200 [thread overview]
Message-ID: <20100315134527.GA31210@mtldesk030.lab.mtl.com> (raw)
In-Reply-To: <20100315111228.GC23358-8YAHvHwT2UEvbXDkjdHOrw/a8Rv0c6iv@public.gmane.org>
I just noticed that Vlad already opened a bugzilla bug (1874) on this.
I quote Sean's response:
RDMA CM supports UD and RC QPs (port spaces UDP/TCP) only. Support
for UC QPs should come from another port space.
This makes sense to me. Still we need to address the issues I raised
below. Sean, are you going to fix this?
On Mon, Mar 15, 2010 at 01:12:28PM +0200, Eli Cohen wrote:
> We got failing tests in our regression that use UC transport from
> userspace. Looking at cma_connect_ib(), I see that it uses IB_QPT_RC
> in the CM request instead of using whatever the transport type of the
> requesting QP. There is no easy way to retrieve that information too
> since the QP is created in userspace. We do have the QP number. One
> way to address this problem is to have an API that returns a pointer
> to struct ib_qp given the ib device and the QP number. Another way
> would be to pass qp_type through the call to rdma_init_qp_attr().
> Thoughts?
--
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:[~2010-03-15 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 11:12 broken support for UC in rdma_cm Eli Cohen
[not found] ` <20100315111228.GC23358-8YAHvHwT2UEvbXDkjdHOrw/a8Rv0c6iv@public.gmane.org>
2010-03-15 13:45 ` Eli Cohen [this message]
[not found] ` <20100315134527.GA31210-8YAHvHwT2UEvbXDkjdHOrw/a8Rv0c6iv@public.gmane.org>
2010-03-15 15:38 ` Sean Hefty
[not found] ` <7E151C5823FF4048B15DCA15845BB0EB-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-03-15 18:48 ` Eli Cohen
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=20100315134527.GA31210@mtldesk030.lab.mtl.com \
--to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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