From: Sowmini Varadhan <sowmini.varadhan@oracle•com>
To: netdev@vger•kernel.org
Cc: davem@davemloft•net, rds-devel@oss•oracle.com,
sowmini.varadhan@oracle•com, santosh.shilimkar@oracle•com
Subject: [PATCH net-next 0/9] RDS:TCP data structure changes for multipath support
Date: Thu, 30 Jun 2016 16:11:09 -0700 [thread overview]
Message-ID: <cover.1467322344.git.sowmini.varadhan@oracle.com> (raw)
The second installment of changes to enable multipath support in
RDS-TCP. This series implements the changes in rds-tcp so that the
rds_conn_path has a pointer to the rds_tcp_connection in cp_transport_data.
Struct rds_tcp_connection keeps track of the inet_sk per path in
t_sock. The ->sk_user_data in turn is a pointer to the rds_conn_path.
With this set of changes, rds_tcp has the needed plumbing to handle
multiple paths(socket) per rds_connection.
Sowmini Varadhan (9):
RDS: Rework path specific indirections
RDS: TCP: Remove dead logic around c_passive in rds-tcp
RDS: TCP: Make rds_tcp_connection track the rds_conn_path
RDS: TCP: Refactor connection destruction to handle multiple paths
RDS: TCP: make ->sk_user_data point to a rds_conn_path
RDS: TCP: make receive path use the rds_conn_path
RDS: TCP: Hooks to set up a single connection path
RDS: TCP: Simplify reconnect to avoid duelling reconnnect attempts
RDS: Do not send a pong to an incoming ping with 0 src port
net/rds/connection.c | 39 ++++++--------
net/rds/ib.c | 8 ++--
net/rds/ib.h | 8 ++--
net/rds/ib_cm.c | 6 ++-
net/rds/ib_recv.c | 3 +-
net/rds/ib_send.c | 3 +-
net/rds/loop.c | 14 +++---
net/rds/rds.h | 7 +--
net/rds/recv.c | 4 ++
net/rds/send.c | 16 ++-----
net/rds/tcp.c | 130 +++++++++++++++++++++++++++++++------------------
net/rds/tcp.h | 22 ++++----
net/rds/tcp_connect.c | 38 ++++++++-------
net/rds/tcp_listen.c | 16 +++---
net/rds/tcp_recv.c | 39 ++++++++-------
net/rds/tcp_send.c | 20 ++++----
net/rds/threads.c | 12 +++-
17 files changed, 211 insertions(+), 174 deletions(-)
next reply other threads:[~2016-06-30 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 23:11 Sowmini Varadhan [this message]
2016-06-30 23:11 ` [PATCH net-next 1/9] RDS: Rework path specific indirections Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 2/9] RDS: TCP: Remove dead logic around c_passive in rds-tcp Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 3/9] RDS: TCP: Make rds_tcp_connection track the rds_conn_path Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 4/9] RDS: TCP: Refactor connection destruction to handle multiple paths Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 5/9] RDS: TCP: make ->sk_user_data point to a rds_conn_path Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 6/9] RDS: TCP: make receive path use the rds_conn_path Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 7/9] RDS: TCP: Hooks to set up a single connection path Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 8/9] RDS: TCP: Simplify reconnect to avoid duelling reconnnect attempts Sowmini Varadhan
2016-06-30 23:11 ` [PATCH net-next 9/9] RDS: Do not send a pong to an incoming ping with 0 src port Sowmini Varadhan
2016-07-01 20:46 ` [PATCH net-next 0/9] RDS:TCP data structure changes for multipath support 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=cover.1467322344.git.sowmini.varadhan@oracle.com \
--to=sowmini.varadhan@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rds-devel@oss$(echo .)oracle.com \
--cc=santosh.shilimkar@oracle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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