From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
Cc: "linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Ilya Nelkenbaum <ilyan-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] libibumad/umad.c: In resolve_ca_port, skip ethernet link layer ports
Date: Thu, 21 Feb 2013 14:59:09 -0500 [thread overview]
Message-ID: <51267C8D.7030002@dev.mellanox.co.il> (raw)
In-Reply-To: <20130221114427.0b82d4054d46a0920dda104e-i2BcT+NCU+M@public.gmane.org>
On 2/21/2013 2:44 PM, Ira Weiny wrote:
> What about QP1? It was my understanding that CM was still required for RoCE.
Yes, RoCE requires CM support but AFAIK CM doesn't use/require these
interfaces to get send or receive it's MADs.
RoCE is a weird animal in terms of IB management as SM/QP0 is not
used/deprecated and QP1 is only required for CM with most other QP1
things beyond the spec with the exception of SA which is also not
used/deprecated.
-- Hal
>
> Ira
>
--
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:[~2013-02-21 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 19:01 [PATCH] libibumad/umad.c: In resolve_ca_port, skip ethernet link layer ports Hal Rosenstock
[not found] ` <51266F1F.608-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-02-21 19:44 ` Ira Weiny
[not found] ` <20130221114427.0b82d4054d46a0920dda104e-i2BcT+NCU+M@public.gmane.org>
2013-02-21 19:59 ` Hal Rosenstock [this message]
[not found] ` <51267C8D.7030002-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-02-21 20:08 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736F35242C-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-02-21 20:38 ` Hal Rosenstock
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=51267C8D.7030002@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=ilyan-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=weiny2-i2BcT+NCU+M@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