linux-kernel - 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1329472239.2861.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
Date:	Fri, 17 Feb 2012 10:50:39 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	"Alex,Shi" <alex.shi@...el.com>
Cc:	davem@...emloft.net,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Tim Chen <tim.c.chen@...el.com>,
	"Huang, Ying" <ying.huang@...el.com>
Subject: Re: TCP_STREAM performance regression on commit b3613118

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 ?

cat /proc/sys/net/ipv4/tcp_rmem
cat /proc/sys/net/ipv4/tcp_wmem
netstat -s


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/