netdev - Re: TCP_STREAM performance regression on commit b3613118

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-next>] [day] [month] [year] [list]

Message-Id: <20120217.133327.1178765872497293871.davem@davemloft.net>
Date:	Fri, 17 Feb 2012 13:33:27 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	alex.shi@...el.com, linux-kernel@...r.kernel.org,
	tim.c.chen@...el.com, ying.huang@...el.com, netdev@...r.kernel.org
Subject: Re: TCP_STREAM performance regression on commit b3613118

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Fri, 17 Feb 2012 10:50:39 +0100

> Le vendredi 17 février 2012 à 16:18 +0800, Alex,Shi a écrit :
>> The tcp_stream loop back performance has about 10% drop on the
>> commitment on our core2 2 sockets server. This commit has 2
>> parents(7505afe28, 5983fe), but both of them have no regression. So
>> guess the impact just happened when this 2 parents joint. That beyond
>> our capability to dig it more.
>> 
>> Any ideas? 
> 
> Most probably the more accurate truesize determination is responsible of
> this tcp regression, since some prior assumptions might be wrong.
> 
> Want to give more information on the workload ?
> Is it a 32 or 64 bit kernel ?

And let's start CC:'ing netdev too.
--
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