netdev - Re: [RFC PATCH 0/5] net: low latency Ethernet device polling

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: <512E7DD1.1010209@candelatech.com>
Date:	Wed, 27 Feb 2013 13:42:41 -0800
From:	Ben Greear <greearb@...delatech.com>
To:	Eliezer Tamir <eliezer.tamir@...ux.intel.com>
CC:	Rick Jones <rick.jones2@...com>,
	Eliezer Tamir <eliezer.tamir@...ux.jf.intel.com>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Dave Miller <davem@...emloft.net>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	e1000-devel@...ts.sourceforge.net,
	Willem de Bruijn <willemb@...gle.com>,
	Andi Kleen <andi@...stfloor.org>, HPA <hpa@...or.com>,
	Eliezer Tamir <eliezer@...ir.org.il>
Subject: Re: [RFC PATCH 0/5] net: low latency Ethernet device polling

On 02/27/2013 12:40 PM, Eliezer Tamir wrote:
> On 27/02/2013 21:58, Rick Jones wrote:
>> On 02/27/2013 09:55 AM, Eliezer Tamir wrote:
>>>
>>> Performance numbers:
>>> Kernel   Config     C3/6  rx-usecs  TCP  UDP
>>> 3.8rc6   typical    off   adaptive  37k  40k
>>> 3.8rc6   typical    off   0*        50k  56k
>>> 3.8rc6   optimized  off   0*        61k  67k
>>> 3.8rc6   optimized  on    adaptive  26k  29k
>>> patched  typical    off   adaptive  70k  78k
>>> patched  optimized  off   adaptive  79k  88k
>>> patched  optimized  off   100       84k  92k
>>> patched  optimized  on    adaptive  83k  91k
>>> *rx-usecs=0 is usually not useful in a production environment.
>>
>> I would think that latency-sensitive folks would be using rx-usecs=0 in
>> production - at least if the NIC in use didn't have low enough latency
>> with its default interrupt coalescing/avoidance heuristics.
>
> It will only work well if you have no bulk traffic on the same port as the low latency traffic at all.

Have you done any tests for bulk throughput with busy-poll?  Yes, it will eat a core,
but that might be worth it in some cases if there was significant throughput increase...

Thanks,
Ben

-- 
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com

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