From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, rds-devel@oss.oracle.com,
ajaykumar.hotchandani@oracle.com, igor.maximov@oracle.com,
chien.yen@oracle.com, sowmini.varadhan@oracle.com,
cwang@twopensource.com, dsahern@gmail.com
Subject: [PATCH v3 net-next 0/2] RDS-TCP: Network namespace support
Date: Wed, 5 Aug 2015 01:43:24 -0400 [thread overview]
Message-ID: <cover.1438752224.git.sowmini.varadhan@oracle.com> (raw)
This patch series contains the set of changes to correctly set up
the infra for PF_RDS sockets that use TCP as the transport in multiple
network namespaces.
Patch 1 in the series is the minimal set of changes to allow
a single instance of RDS-TCP to run in any (i.e init_net or other) net
namespace. The changes in this patch set ensure that the execution of
'modprobe [-r] rds_tcp' sets up the kernel TCP sockets
relative to the current netns, so that RDS applications can send/recv
packets from that netns, and the netns can later be deleted cleanly.
Patch 2 of the series further allows multiple RDS-TCP instances,
one per network namespace. The changes in this patch allows dynamic
creation/tear-down of RDS-TCP client and server sockets across all
current and future namespaces.
v2 changes from RFC sent out earlier:
David Ahern comments in patch 1, net_device notifier in patch 2,
patch 3 broken off and submitted separately.
v3: Cong Wang review comments.
Sowmini Varadhan (2):
Make RDS-TCP work correctly when it is set up in a netns other than
init_net
Support multiple RDS-TCP listen endpoints, one per netns.
net/rds/bind.c | 3 +-
net/rds/connection.c | 16 +++--
net/rds/ib.c | 2 +-
net/rds/ib_cm.c | 5 +-
net/rds/iw.c | 2 +-
net/rds/iw_cm.c | 5 +-
net/rds/rds.h | 23 ++++++-
net/rds/send.c | 3 +-
net/rds/tcp.c | 165 +++++++++++++++++++++++++++++++++++++++++++-----
net/rds/tcp.h | 7 ++-
net/rds/tcp_connect.c | 9 ++-
net/rds/tcp_listen.c | 40 ++++--------
net/rds/transport.c | 4 +-
13 files changed, 214 insertions(+), 70 deletions(-)
next reply other threads:[~2015-08-05 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 5:43 Sowmini Varadhan [this message]
2015-08-05 5:43 ` [PATCH v3 net-next 1/2] RDS-TCP: Make RDS-TCP work correctly when it is set up in a netns other than init_net Sowmini Varadhan
2015-08-05 5:43 ` [PATCH v3 net-next 2/2] RDS-TCP: Support multiple RDS-TCP listen endpoints, one per netns Sowmini Varadhan
2015-08-07 18:30 ` [PATCH v3 net-next 0/2] RDS-TCP: Network namespace 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.1438752224.git.sowmini.varadhan@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=ajaykumar.hotchandani@oracle.com \
--cc=chien.yen@oracle.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=igor.maximov@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.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).