public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
Cc: "Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Patrick McHardy <kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
Subject: Re: using same IP subnet on multiple interfaces
Date: Mon, 16 Aug 2010 21:19:45 -0600	[thread overview]
Message-ID: <20100817031945.GA5251@obsidianresearch.com> (raw)
In-Reply-To: <4C69597C.2040008-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>

On Mon, Aug 16, 2010 at 06:30:04PM +0300, Or Gerlitz wrote:

> As for the original issue we were discussing here, Sean - the
> conclusion is that with upstream 2.6.35 bits for the rdma connection
> to go from hca1 port1 to hca1 port2 (or from hca1 port1 to hca2
> port1), the rdma-cm needs a neighbour, similarly to a ping -I ib0 to
> ib1 address.
> 
> A neighbour isn't created unless the responding NIC (ib1 in my
> example) has both rp_filter set to 0 and accept_local set to 1,
> Jason, does this makes sense?

This description seemed reasonable to me. It is pretty confusing what
binding means in RDMA CM, it is different then sockets, and is some
combination of SO_BINDTODEVICE and bind to address.

Also, you might find the fixes that were done lately for IPv6 tidied
up some of the general routing and device select stuff that becomes
noticable when you start doing funny routing things like this.

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

  parent reply	other threads:[~2010-08-17  3:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 15:42 dual HCAs with upstream kernel Hefty, Sean
     [not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25A9687B2B-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-08-15  7:50   ` using same IP subnet on multiple interfaces (was: dual HCAs with upstream kernel) Or Gerlitz
     [not found]     ` <4C679C39.8060709-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-08-15 16:59       ` Jason Gunthorpe
     [not found]         ` <20100815165946.GA2861-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-08-16 15:30           ` using same IP subnet on multiple interfaces Or Gerlitz
     [not found]             ` <4C69597C.2040008-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-08-17  3:19               ` Jason Gunthorpe [this message]
     [not found]                 ` <20100817031945.GA5251-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-08-18  6:02                   ` Or Gerlitz

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=20100817031945.GA5251@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@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