From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, rds-devel@oss.oracle.com,
sowmini.varadhan@oracle.com
Subject: Re: [PATCH v5 net-next 3/3] rds: Extend RDS API for IPv6 support
Date: Mon, 23 Jul 2018 21:16:39 -0700 [thread overview]
Message-ID: <7b7ec326-5519-2fa9-044c-ada28e572747@oracle.com> (raw)
In-Reply-To: <cbb2d34e7b627f8a89f3d774aee585c6945e048f.1532404047.git.ka-cheong.poon@oracle.com>
On 7/23/18 8:51 PM, Ka-Cheong Poon wrote:
> There are many data structures (RDS socket options) used by RDS apps
> which use a 32 bit integer to store IP address. To support IPv6,
> struct in6_addr needs to be used. To ensure backward compatibility, a
> new data structure is introduced for each of those data structures
> which use a 32 bit integer to represent an IP address. And new socket
> options are introduced to use those new structures. This means that
> existing apps should work without a problem with the new RDS module.
> For apps which want to use IPv6, those new data structures and socket
> options can be used. IPv4 mapped address is used to represent IPv4
> address in the new data structures.
>
> v4: Revert changes to SO_RDS_TRANSPORT
>
> Signed-off-by: Ka-Cheong Poon<ka-cheong.poon@oracle.com>
> ---
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
next prev parent reply other threads:[~2018-07-24 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 3:51 [PATCH v5 net-next 0/3] rds: IPv6 support Ka-Cheong Poon
2018-07-24 3:51 ` [PATCH v5 net-next 1/3] rds: Changing IP address internal representation to struct in6_addr Ka-Cheong Poon
2018-07-24 4:15 ` santosh.shilimkar
2018-07-24 3:51 ` [PATCH v5 net-next 2/3] rds: Enable RDS IPv6 support Ka-Cheong Poon
2018-07-24 4:16 ` santosh.shilimkar
2018-07-24 3:51 ` [PATCH v5 net-next 3/3] rds: Extend RDS API for " Ka-Cheong Poon
2018-07-24 4:16 ` santosh.shilimkar [this message]
2018-07-24 4:06 ` [PATCH v5 net-next 0/3] rds: " David Miller
2018-07-24 4:18 ` David Miller
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=7b7ec326-5519-2fa9-044c-ada28e572747@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).