From: Shawn Bohrer <sbohrer-EgGFQ3RFNTIP7C3xziwOQw@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Linux 3.2-rc1 vs. OFED 1.5.4-rc4: Packets are looped back
Date: Thu, 17 Nov 2011 17:33:09 +0000 (UTC) [thread overview]
Message-ID: <loom.20111117T182134-82@post.gmane.org> (raw)
In-Reply-To: alpine.DEB.2.00.1111111007550.10404@router.home
Christoph Lameter <cl@...> writes:
>
> We have an app here that runs fine with OFED. But if I try to use the
> kernel IB subsystem in 3.2 it complains about packets being looped back to
> the application.
>
> That seems to be controlled by IB_DEVICE_BLOCK_MULTICAST_LOOPBACK and
> IB_QP_CREATE_BLOCK_MULTICAST_LOOPBACK.
>
> Why does it not work in the kernel IB stack?
The only place the 3.2 kernel sets IB_QP_CREATE_BLOCK_MULTICAST_LOOPBACK is in
ipoib_transport_dev_init() so unless you are doing IPoIB you will get loopback
traffic.
The reason you do not get loopback traffic with OFED is because OFED has the
following patch that adds the block_loopback module parameter to mlx4_core and
defaults to blocking-enabled.
http://git.openfabrics.org/git?p=ofed_1_5/linux-2.6.git;a=blob;f=kernel_patches/fixes/mlx4_0290_mcast_loopback.patch;h=786a3926529befac2c2d1fa6d8c36bada79d61a7;hb=HEAD
--
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:[~2011-11-17 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 16:14 Linux 3.2-rc1 vs. OFED 1.5.4-rc4: Packets are looped back Christoph Lameter
2011-11-17 17:33 ` Shawn Bohrer [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=loom.20111117T182134-82@post.gmane.org \
--to=sbohrer-eggfq3rfntip7c3xziwoqw@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