From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, rds-devel@oss.oracle.com
Subject: Re: [PATCH net-next 3/5] RDS: TCP: Enable multipath RDS for TCP
Date: Thu, 14 Jul 2016 09:47:46 -0700 [thread overview]
Message-ID: <a06d31cc-bc19-476a-1c68-b396d0cb8f09@oracle.com> (raw)
In-Reply-To: <7a00f744a33192a5126b30419f7526795ab77cae.1468488884.git.sowmini.varadhan@oracle.com>
On 7/14/2016 3:51 AM, Sowmini Varadhan wrote:
> Use RDS probe-ping to compute how many paths may be used with
> the peer, and to synchronously start the multiple paths. If mprds is
> supported, hash outgoing traffic to one of multiple paths in rds_sendmsg()
> when multipath RDS is supported by the transport.
>
> CC: Santosh Shilimkar <santosh.shilimkar@oracle.com>
> Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
> ---
Thanks for updating the earlier version discussed off-list.
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
next prev parent reply other threads:[~2016-07-14 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 10:51 [PATCH net-next 0/5] RDS: TCP: Enable mprds for rds-tcp Sowmini Varadhan
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 [this message]
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=a06d31cc-bc19-476a-1c68-b396d0cb8f09@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=davem@davemloft.net \
--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).