Date: Thu, 17 Mar 2016 15:58:27 +0000 From: "Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com> To: Eric van Gyzen <vangyzen@FreeBSD.org>, Alan Somers <asomers@freebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Jack Vogel <jfvogel@gmail.com> Subject: RE: TSO test Message-ID: <2A35EA60C3C77D438915767F458D656880953C37@ORSMSX111.amr.corp.intel.com> In-Reply-To: <56EAD3A2.4020507@FreeBSD.org> References: <CAFOYbcn9XTaLrtZhkS1X69qhf2aOe0iOSirCTA=LfGsZDTqbeg@mail.gmail.com> <2A35EA60C3C77D438915767F458D656880953A88@ORSMSX111.amr.corp.intel.com> <CAOtMX2g7NzquGC17Gz5dXHEOy7nQFGEhb7FrBPO0zrXDwH=d6g@mail.gmail.com> <56EACBCF.5020109@FreeBSD.org> <2A35EA60C3C77D438915767F458D656880953B86@ORSMSX111.amr.corp.intel.com> <56EAD3A2.4020507@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
No, we have scripts that parse vmstat -i. Jeff -----Original Message----- From: Eric van Gyzen [mailto:vangyzen@FreeBSD.org]=20 Sent: Thursday, March 17, 2016 8:56 AM To: Pieper, Jeffrey E <jeffrey.e.pieper@intel.com>; Alan Somers <asomers@fr= eebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org>; Jack Vogel <jfvogel@gmail.com> Subject: Re: TSO test Jeff, So, you reboot the DUT between each scenario? Eric On 03/17/2016 10:28, Pieper, Jeffrey E wrote: > You can also parse vmstat -i, which we do as well. >=20 > Jeff >=20 > -----Original Message----- > From: Eric van Gyzen [mailto:vangyzen@FreeBSD.org]=20 > Sent: Thursday, March 17, 2016 8:23 AM > To: Alan Somers <asomers@freebsd.org>; Pieper, Jeffrey E <jeffrey.e.piepe= r@intel.com> > Cc: FreeBSD Net <freebsd-net@freebsd.org>; Jack Vogel <jfvogel@gmail.com> > Subject: Re: TSO test >=20 > Alan, >=20 > 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 opini= on. >=20 > Cheers, >=20 > Eric >=20 > 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.o= rg] >>> On Behalf Of Jack Vogel >>> Sent: Wednesday, March 16, 2016 11:31 PM >>> To: FreeBSD Net <freebsd-net@freebsd.org> >>> 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" >> >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2A35EA60C3C77D438915767F458D656880953C37>