Date: Tue, 16 Apr 2013 20:24:49 +0800 From: Sepherosa Ziehau <sepherosa@gmail.com> To: Bruce Evans <brde@optusnet.com.au> Cc: "pyunyh@gmail.com" <pyunyh@gmail.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, David Christensen <davidch@broadcom.com>, bde <bde@freebsd.org> Subject: Re: bge(4) sysctl tuneables -- a blast from the past. Message-ID: <CAMOc5cyrgh1szyrEKTzAEQ4-egtD4XmYxp%2B13SyZizVXiEhfEA@mail.gmail.com> In-Reply-To: <20130416152121.G904@besplex.bde.org> References: <1365781568.1418.1.camel@localhost> <20130413200512.G1165@besplex.bde.org> <1366065356.1350.7.camel@localhost> <20130416152121.G904@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 16, 2013 at 1:56 PM, Bruce Evans <brde@optusnet.com.au> wrote: > > Technical bugs include: > - wrong defaults are claimed for *coal_ticks. The defaults are 150, but > are claimed to be 150 milliseconds. These values are dimensionless, > but since ticks take 1 microsecond each, 150 gives 150 microseconds, > not 150 milliseconds. The real effect of TX coalesce ticks is confusing to me; TX interrupt does not come at the rate you have specified, at least for several PCI-e bge(4) I have tested. However, RX coalesce ticks work as expected. Here is how the tests were conducted: - Send only test, no RX - Each packet consume only one BD; UDP datagram, using hardware checksum offloading - TX coalesce BDs is set to 0, so only TX coalesce ticks have effect The interrupt rate I had got seemed to be related to packet size?! I had tested two TX coalesce ticks settings: (the result I had recorded was using BCM5720) The first setting was 1023us; the first col is UDP data size, the second col is rough interrupt rate 18B 667/s 64B 611/s 128B 538/s 256B 432/s 512B 311/s 1024B 194/s 1472B 146/s Tecond setting was 128us; the first col is UDP data size, the second col is rough interrupt rate 18B 1647/s 64B 1338/s 128B 1030/s 256B 700/s 512B 430/s 1024B 235/s 1472B 169/s Well, to be frank, it does not make too much sense to me. I also twisted the HCC_MODE CLRTICK_TX a bit, but didn't get determined result. (davidch is CC'd) Best Regards, sephe -- Tomorrow Will Never Die
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMOc5cyrgh1szyrEKTzAEQ4-egtD4XmYxp%2B13SyZizVXiEhfEA>