netdev - Re: [PATCH net-next 0/5] RDS: TCP: Enable mprds for rds-tcp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 15 Jul 2016 11:38:11 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sowmini.varadhan@...cle.com
Cc:	netdev@...r.kernel.org, rds-devel@....oracle.com,
	santosh.shilimkar@...cle.com
Subject: Re: [PATCH net-next 0/5] RDS: TCP: Enable mprds for rds-tcp

From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Date: Thu, 14 Jul 2016 03:51:00 -0700

> 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.

Series applied, thanks.