netdev - Re: [PATCH v2 net-next 0/3] RDS: RDS-TCP perf enhancements

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20151005.033547.905125073688788587.davem@davemloft.net>
Date:	Mon, 05 Oct 2015 03:35:47 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sowmini.varadhan@...cle.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	rds-devel@....oracle.com, ajaykumar.hotchandani@...cle.com,
	igor.maximov@...cle.com, santosh.shilimkar@...cle.com,
	sergei.shtylyov@...entembedded.com
Subject: Re: [PATCH v2 net-next 0/3] RDS: RDS-TCP perf enhancements

From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Date: Wed, 30 Sep 2015 16:54:06 -0400

> A 3-part patchset that (a) improves current RDS-TCP perf
> by 2X-3X and (b) refactors earlier robustness code for
> better observability/scaling.
> 
> Patch 1 is an enhancment of earlier robustness fixes 
> that had used separate sockets for client and server endpoints to
> resolve race conditions. It is possible to have an equivalent
> solution that does not use 2 sockets. The benefit of a
> single socket solution is that it results in more predictable
> and observable behavior for the underlying TCP pipe of an 
> RDS connection
> 
> Patches 2 and 3 are simple, straightforward perf bug fixes
> that align the RDS TCP socket with other parts of the kernel stack.
> 
> v2: fix kbuild-test-robot warnings, comments from  Sergei Shtylov
>     and Santosh Shilimkar. 

Series applied to net-next, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html