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: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"David J. Wilder"
	<dwilder-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	Or Gerlitz <or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
	linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Aleksey Senin <alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: rping is not resolving ipv6 addresses
Date: Sun, 11 Oct 2009 13:52:46 -0600	[thread overview]
Message-ID: <20091011195246.GA1397@obsidianresearch.com> (raw)
In-Reply-To: <4AD18944.1040404-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>

On Sun, Oct 11, 2009 at 09:29:08AM +0200, Or Gerlitz wrote:
> Sean Hefty wrote:
> > The rdma cm was never fully coded or tested for ipv6 support.
 
> Sean, even if not fully coded/tested, some work has been done, e.g
> commits 38617c64 "RDMA/addr: Add support for translating IPv6
> addresses" and 1f5175ad "RDMA/cma: Add IPv6 support". I suggest
> we'll try to see what does it take to make this better or even fully
> support ipv6.

Or is right, these are kernel bugs, if nobody is able to work on them
then I think we all have to accept that these parts of the OFA stack
are unfinished and unmaintained - and see if that can be delt with.

> Jason, can you restate what are the two problems you saw from
> David's reports? the 1st was related to scope in link-local
> addresses, and what's the 2nd?

The kernel must not accept a link local address with 0 scope id

When using link local addresses the kernel must bind to the interface
index in the scope id.

The scope is ignored for other addresses scopes.

The rules will be more complex if a source and dest are specified, in
that case the scopes must match.

This is the same basic problem as the other issues regarding ND and
route resolution, the RDMA CM does not follow the same procedures as
TCP does, and the variations produce bugs.

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:[~2009-10-11 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1254957121.23471.17.camel@wilder.ibm.com>
     [not found] ` <adavdiqn63u.fsf@cisco.com>
     [not found]   ` <1255114672.3533.8.camel@wilder.ibm.com>
     [not found]     ` <1255114672.3533.8.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-10-09 20:53       ` [ewg] rping is not resolving ipv6 addresses Or Gerlitz
     [not found]         ` <15ddcffd0910091353w51bddc60w8452ca107de296fb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-09 21:15           ` David J. Wilder
     [not found]             ` <1255122901.3533.20.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-10-09 21:22               ` Or Gerlitz
2009-10-09 22:46               ` Jason Gunthorpe
     [not found]                 ` <20091009224604.GG5191-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-10-09 23:02                   ` Sean Hefty
     [not found]                     ` <0AA9B9870A0545E6BCCF3A5EF4BAB34E-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-10-11  7:29                       ` Or Gerlitz
     [not found]                         ` <4AD18944.1040404-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-10-11 19:52                           ` Jason Gunthorpe [this message]
2009-10-12 17:52                   ` [ewg] " David J. Wilder
     [not found]                     ` <1255369979.29677.7.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-10-12 19:47                       ` Jason Gunthorpe

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=20091011195246.GA1397@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    --cc=dwilder-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org \
    --cc=or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@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