From: "David J. Wilder" <dwilder-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
Cc: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 8/9] ib/addr: simplify resolving IPv4 addresses
Date: Thu, 19 Nov 2009 08:46:49 -0800 [thread overview]
Message-ID: <1258649210.11975.34.camel@wilder.ibm.com> (raw)
In-Reply-To: <4B055BBA.8020505-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
On Thu, 2009-11-19 at 16:52 +0200, Or Gerlitz wrote:
> > I reviewed patches 1-6 & 8 and they all look fine, I will give the whole series
> > a try later this week to further validate them
>
I tested ipv4 and ipv6 address resolution using ucmatose. All my tests
ran fine. I tested with patches 1 through 9 on ofed
1.5(OFED-1.5-20091118-0600) on 2.6.30. Ucmatose was taken from Sean's
librdmacm git (required for ipv6 support). Here are the tests I ran:
ucmatose
[-s server_address]
[-b bind_address]
ipv4 - Local address
----------------------
ucmatose -s 127.0.0.1
ucmatose -s 192.168.0.199
ucmatose -b 192.168.0.199 -s 192.168.0.199
ipv4 - Remote address
----------------------
ucmatose -s 192.168.0.198
ucmatose -b 192.168.0.199 -s 192.168.0.198
ipv6 - Local addresses
-----------------------
ucmatose -s fe80::202:c903:1:28ed%ib0
ucmatose -s 2001:db8:1234::1
ucmatose -b fe80::202:c903:1:28ed%ib0 -s fe80::202:c903:1:28ed%ib0
ucmatose -b 2001:db8:1234::1 -s 2001:db8:1234::1
ucmatose -b 2001:db8:1234::1 -s fe80::202:c903:1:28ed%ib0
ucmatose -b fe80::202:c903:1:28ee%ib1 -s 2001:db8:1234::1
ucmatose -b 2001:db8:1234::10 -s 2001:db8:1234::1
ipv6 - Remote addresses
------------------------
ucmatose -s 2001:db8:1234::2
ucmatose -b 2001:db8:1234::1 -s 2001:db8:1234::2
ucmatose -b fe80::202:c903:1:28ed%ib0 -s 2001:db8:1234::2
ucmatose -b fe80::202:c903:1:28ee%ib1 -s 2001:db8:1234::2
ucmatose -s fe80::202:c903:1:1925%ib0
ucmatose -b 2001:db8:1234::1 -s fe80::202:c903:1:1925%ib0
ucmatose -b fe80::202:c903:1:28ed%ib0 -s fe80::202:c903:1:1925%ib0
--
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:[~2009-11-19 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 0:07 [PATCH 8/9] ib/addr: simplify resolving IPv4 addresses Sean Hefty
[not found] ` <AD17449F0C4E4FE7B20C32412F077C00-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-11-17 6:27 ` Or Gerlitz
[not found] ` <4B024258.7070500-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-11-17 20:51 ` David J. Wilder
[not found] ` <1258491091.11975.1.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-11-17 21:26 ` Sean Hefty
2009-11-19 14:52 ` Or Gerlitz
[not found] ` <4B055BBA.8020505-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-11-19 16:46 ` David J. Wilder [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=1258649210.11975.34.camel@wilder.ibm.com \
--to=dwilder-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@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