Date: Wed, 17 Aug 2011 09:15:34 +0100 From: Andrew Stevenson <andrew@ugh.net.au> To: =?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com> Cc: pyunyh@gmail.com, embedded@freebsd.org, net@freebsd.org Subject: Re: system locks up with vr driver on alix board Message-ID: <C38D5CC3-F227-4F27-9A85-AB5F135FB300@ugh.net.au> In-Reply-To: <C64CDCB3-A1DE-48CF-BEE5-54BA7084B3CB@develooper.com> References: <D8B41107-90ED-4357-A7DA-4FF987C70567@develooper.com> <4E4AB3BE.4090603@sentex.net> <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com> <20110817002911.GA7614@michelle.cdnetworks.com> <C64CDCB3-A1DE-48CF-BEE5-54BA7084B3CB@develooper.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Aug 2011, at 02:39, Ask Bj=F8rn Hansen wrote: >> How many PPS or interrupts do you see from vr interface under high >> network load? >=20 > Honestly I'm not sure. I only know how to see the interrupt busy = percentage from top =85 Is there a cheap way to get those numbers? = If so then I'll log them every second or two and see if it catches = anything. "systat -vmstat" shows interrupts per second per device. Some use of awk = or sed may be required. HTH, Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C38D5CC3-F227-4F27-9A85-AB5F135FB300>