[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <519B7355.9090303@mellanox.com>
Date: Tue, 21 May 2013 16:15:01 +0300
From: Alex Rosenbaum <alexr@...lanox.com>
To: Eliezer Tamir <eliezer.tamir@...ux.intel.com>
CC: Dave Miller <davem@...emloft.net>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Don Skidmore <donald.c.skidmore@...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: [PATCH v3 net-next 0/4] net: low latency Ethernet device polling
On 5/21/2013 3:29 PM, Eliezer Tamir wrote:
> What benchmarks are you using to test poll/select/epoll?
for epoll/select latency tests we are using sockperf as performance
latency tool: https://code.google.com/p/sockperf/
It is a client-server based tool and it supported ping-pong, throughput,
and under-load test type.
For epoll, you will need to define a 'feedfile' ("-f filepathname")
which has a list of TCP and/or UDP socket and defined your IO mux type
("-F epoll").
thanks for all the clarifications.
- Alex Rosenbaum
--
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
Powered by blists - more mailing lists