From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>,
Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, rds-devel@oss.oracle.com
Subject: Re: [PATCH net-next 2/3] rds: Enable RDS IPv6 support
Date: Wed, 27 Jun 2018 13:45:13 -0700 [thread overview]
Message-ID: <4bccd9bf-4858-4c9f-aac1-d25a8083ac09@oracle.com> (raw)
In-Reply-To: <e83dbf4a-b813-4edc-9245-d738faaedb4b@oracle.com>
On 6/27/2018 3:07 AM, Ka-Cheong Poon wrote:
> On 06/26/2018 09:08 PM, Sowmini Varadhan wrote:
>> On (06/26/18 21:02), Ka-Cheong Poon wrote:
[...]
>
>
> I don't expect RDS apps will want to use link local address
> in the first place. In fact, most normal network apps don't.
>
This is not true.
>
>> You're not doing this for IPv4 and RDS today (you dont have to do this
>> for UDP, afaik)
>
>
> Do you know of any IPv4 RDS app which uses IPv4 link local
> address? In fact, IPv4 link local address is explicitly
> disallowed for active active bonding.
>
Yes. Cluster-ware HAIP makes use of link local addresses. That
check was mainly because of RDMA CM issues but that only means
active-active isn't used. The bonding works just fine and if
needed cluster-ware can also use TCP transport.
Lets not add this new behavior for link local and its
actually not relevant to really v6 addressing support.
Regards,
Santosh
next prev parent reply other threads:[~2018-06-27 20:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 10:38 [PATCH net-next 0/3] rds: IPv6 support Ka-Cheong Poon
2018-06-25 10:38 ` [PATCH net-next 1/3] rds: Changing IP address internal representation to struct in6_addr Ka-Cheong Poon
2018-06-25 13:39 ` [RFC PATCH] rds: rds_rdma_cm_event_handler_cmn() can be static kbuild test robot
2018-06-25 13:39 ` [PATCH net-next 1/3] rds: Changing IP address internal representation to struct in6_addr kbuild test robot
2018-06-25 10:38 ` [PATCH net-next 2/3] rds: Enable RDS IPv6 support Ka-Cheong Poon
2018-06-25 14:52 ` kbuild test robot
2018-06-25 17:03 ` Sowmini Varadhan
2018-06-25 17:43 ` Ka-Cheong Poon
2018-06-25 17:50 ` Sowmini Varadhan
2018-06-25 18:44 ` Santosh Shilimkar
2018-06-26 5:30 ` Ka-Cheong Poon
2018-06-26 10:16 ` Sowmini Varadhan
2018-06-26 13:02 ` Ka-Cheong Poon
2018-06-26 13:08 ` Sowmini Varadhan
2018-06-27 10:07 ` Ka-Cheong Poon
2018-06-27 10:29 ` Sowmini Varadhan
2018-06-27 20:45 ` Santosh Shilimkar [this message]
2018-06-25 10:38 ` [PATCH net-next 3/3] rds: Extend RDS API for " Ka-Cheong Poon
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=4bccd9bf-4858-4c9f-aac1-d25a8083ac09@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=davem@davemloft.net \
--cc=ka-cheong.poon@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=sowmini.varadhan@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).