netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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/5] RDS: TCP: Enable mprds for rds-tcp
Date: Thu, 14 Jul 2016 03:51:00 -0700	[thread overview]
Message-ID: <cover.1468488884.git.sowmini.varadhan@oracle.com> (raw)


The third, and final, installment for mprds-tcp changes.

In Patch 3 of this set, if the transport support t_mp_capable, 
we hash outgoing traffic across multiple paths.  Additionally, even if 
the transport is MP capable, we may be peering with some node that does
not support mprds, or supports a different number of paths. This
necessitates RDS control plane changes so that both peers agree
on the number of paths to be used for the rds-tcp connection.
Patch 3 implements all these changes, which are documented in patch 5
of the series.

Patch 1 of this series is a bug fix for a race-condition
that has always existed, but is now more easily encountered with mprds. 
Patch 2 is code refactoring. Patches 4 and 5 are Documentation updates.

Sowmini Varadhan (5):
  RDS: TCP: avoid bad page reference in rds_tcp_listen_data_ready
  RDS: TCP: Reduce code duplication in rds_tcp_reset_callbacks()
  RDS: TCP: Enable multipath RDS for TCP
  Documentation: RDS: updates for SO_RDS_TRANSPORT socket option
  Documentation: RDS: Document Multipath RDS (mprds)

 Documentation/networking/rds.txt |   72 ++++++++++++++++++++++++++++++++++++-
 net/rds/bind.c                   |    6 +++
 net/rds/connection.c             |   17 ++++-----
 net/rds/message.c                |    1 +
 net/rds/rds.h                    |   25 ++++++++++++-
 net/rds/recv.c                   |   75 ++++++++++++++++++++++++++++++++++++++
 net/rds/send.c                   |   71 ++++++++++++++++++++++++++++++++++--
 net/rds/tcp.c                    |   31 ++++++----------
 net/rds/tcp.h                    |    1 +
 net/rds/tcp_connect.c            |    7 +++-
 net/rds/tcp_listen.c             |   65 +++++++++++++++++++++++++++++----
 net/rds/tcp_send.c               |   18 +++++++---
 net/rds/threads.c                |    2 +
 13 files changed, 342 insertions(+), 49 deletions(-)

             reply	other threads:[~2016-07-14 10:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 10:51 Sowmini Varadhan [this message]
2016-07-14 10:51 ` [PATCH net-next 1/5] RDS: TCP: avoid bad page reference in rds_tcp_listen_data_ready Sowmini Varadhan
2016-07-14 10:51 ` [PATCH net-next 2/5] RDS: TCP: Reduce code duplication in rds_tcp_reset_callbacks() Sowmini Varadhan
2016-07-14 10:51 ` [PATCH net-next 3/5] RDS: TCP: Enable multipath RDS for TCP Sowmini Varadhan
2016-07-14 16:47   ` Santosh Shilimkar
2016-07-14 10:51 ` [PATCH net-next 4/5] Documentation: RDS: updates for SO_RDS_TRANSPORT socket option Sowmini Varadhan
2016-07-14 10:51 ` [PATCH net-next 5/5] Documentation: RDS: Document Multipath RDS (mprds) Sowmini Varadhan
2016-07-15 18:38 ` [PATCH net-next 0/5] RDS: TCP: Enable mprds for rds-tcp 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.1468488884.git.sowmini.varadhan@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=davem@davemloft.net \
    --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 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).