From owner-freebsd-net@freebsd.org Thu Mar 17 15:22:56 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0831AD3FE1 for ; Thu, 17 Mar 2016 15:22:56 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) by mx1.freebsd.org (Postfix) with ESMTP id 99C02895; Thu, 17 Mar 2016 15:22:56 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 1DB2956498; Thu, 17 Mar 2016 10:22:56 -0500 (CDT) Subject: Re: TSO test To: Alan Somers , "Pieper, Jeffrey E" References: <2A35EA60C3C77D438915767F458D656880953A88@ORSMSX111.amr.corp.intel.com> Cc: FreeBSD Net , Jack Vogel From: Eric van Gyzen Message-ID: <56EACBCF.5020109@FreeBSD.org> Date: Thu, 17 Mar 2016 10:22:55 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2016 15:22:56 -0000 Alan, That does sound useful. As one complication, "vmstat -i" shows the interrupt rate since boot. Either the test would need to reboot between each iteration, or vmstat would need to be improved to show the "recent" rate. The latter would be a much welcome improvement, in my humble opinion. Cheers, Eric On 03/17/2016 09:45, Alan Somers wrote: > Would it be more useful to log the NIC's interrupt rate using "vmstat -i"? > > On Thu, Mar 17, 2016 at 8:25 AM, Pieper, Jeffrey E < > jeffrey.e.pieper@intel.com> wrote: > >> Basically what we do is run TCP tx traffic using various message sizes >> with TSO enabled, while logging throughput and CPU usage, then run the same >> scenario again with TSO disabled. We do this with both IPv4 and IPv6. >> >> Jeff >> >> -----Original Message----- >> From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] >> On Behalf Of Jack Vogel >> Sent: Wednesday, March 16, 2016 11:31 PM >> To: FreeBSD Net >> Subject: TSO test >> >> Anyone have a 'simple' test case for TSO, something a bit >> more distilled than running netperf or iperf? >> >> Thanks, >> >> Jack >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >