From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Cc: Santosh Shilimkar <santosh.shilimkar@oracle.com>,
davem@davemloft.net, netdev@vger.kernel.org,
rds-devel@oss.oracle.com
Subject: Re: [PATCH v2 net-next 1/3] rds: Changing IP address internal representation to struct in6_addr
Date: Fri, 6 Jul 2018 11:25:58 -0400 [thread overview]
Message-ID: <20180706152558.GJ30983@oracle.com> (raw)
In-Reply-To: <64196e9e-bb90-9452-5fbf-2004e2bd68e3@oracle.com>
On (07/06/18 23:08), Ka-Cheong Poon wrote:
>
> As mentioned in a previous mail, it is unclear why the
> port number is transport specific. Most Internet services
> use the same port number running over TCP/UDP as shown
> in the IANA database. And the IANA RDS registration is
> the same. What is the rationale of having a transport
> specific number in the RDS implementation?
because not every transport may need a port number.
e.g., "RDS over pigeon carrier" may not need a port number.
in a different design (e.g., KCM) the listen port is configurable
with sysctl
Some may need more than one, e.g., rds_rdma, evidently.
What is the problem with using the unused 18635 for the RDS_CM_PORT?
next prev parent reply other threads:[~2018-07-06 15:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 10:23 [PATCH v2 net-next 0/3] rds: IPv6 support Ka-Cheong Poon
2018-06-27 10:23 ` [PATCH v2 net-next 1/3] rds: Changing IP address internal representation to struct in6_addr Ka-Cheong Poon
2018-06-30 8:50 ` David Miller
2018-07-03 14:02 ` Ka-Cheong Poon
2018-07-05 17:58 ` Santosh Shilimkar
2018-07-06 9:08 ` Ka-Cheong Poon
2018-07-06 10:15 ` Sowmini Varadhan
2018-07-06 15:08 ` Ka-Cheong Poon
2018-07-06 15:25 ` Sowmini Varadhan [this message]
2018-07-06 17:26 ` Santosh Shilimkar
2018-07-09 12:26 ` Ka-Cheong Poon
2018-07-06 14:55 ` santosh.shilimkar
2018-06-27 10:23 ` [PATCH v2 net-next 2/3] rds: Enable RDS IPv6 support Ka-Cheong Poon
2018-06-27 10:23 ` [PATCH v2 net-next 3/3] rds: Extend RDS API for " Ka-Cheong Poon
2018-07-05 17:44 ` [PATCH v2 net-next 0/3] rds: " Sowmini Varadhan
2018-07-06 14:36 ` Ka-Cheong Poon
2018-07-06 15:14 ` Sowmini Varadhan
2018-07-09 12:24 ` 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=20180706152558.GJ30983@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=ka-cheong.poon@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.