netdev - Re: [RFCv4 PATCH 2/2] net: Allow protocols to provide an unlocked

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: <9b2db90b0910010249h182bf5d4sc7fdaea9e1345720@mail.gmail.com>
Date:	Thu, 1 Oct 2009 11:49:39 +0200
From:	Nir Tzachar <nir.tzachar@...il.com>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Linux Networking Development Mailing List 
	<netdev@...r.kernel.org>
Cc:	Ziv Ayalon <ziv@...al.co.il>
Subject: Re: [RFCv4 PATCH 2/2] net: Allow protocols to provide an 
	unlocked_recvmsg socket method

Hi Arnaldo

I have repeated the tests using net-next on top of linus' git tree (I
hope I got it right..) and the patches you sent me. Things did not get
better, and in most cases were even worse; the recvmmsg parts
distinctly showed better throughput, but the latency has more than
doubled.

The simplest test of using a batch size of 1 results with recvmmsg's
latency over 1000 micro, while regular recvmsg is around 450 micro.
(note that to use 1 packet there is a small bug in the reg_recv which
needs to be fixed. Namely, change ret = -1 to ret = 0). On the
previous system config -- part 0001 of the patch, on top of 2.6.31 --
the latency of a single packet batch is 370 micro.

So, there seems to be a regression with the kernel tree I am using, or
with part 0002 of the path. I'll try running the net-next with only
part 1 of the patch and report.

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