From owner-freebsd-current@FreeBSD.ORG  Thu Mar 12 21:36:56 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9A68D106566B
	for <current@freebsd.org>; Thu, 12 Mar 2009 21:36:56 +0000 (UTC)
	(envelope-from chris@young-alumni.com)
Received: from mail.oldschoolpunx.net (cpe-72-177-10-243.austin.res.rr.com
	[72.177.10.243])
	by mx1.freebsd.org (Postfix) with ESMTP id 64DCC8FC14
	for <current@freebsd.org>; Thu, 12 Mar 2009 21:36:56 +0000 (UTC)
	(envelope-from chris@young-alumni.com)
Received: by mail.oldschoolpunx.net (Postfix, from userid 58)
	id 16FD295B02; Thu, 12 Mar 2009 16:21:18 -0500 (CDT)
Received: from [192.168.8.100] (unknown [192.168.8.100])
	by mail.oldschoolpunx.net (Postfix) with ESMTPSA id 5174595A95
	for <current@freebsd.org>; Thu, 12 Mar 2009 16:17:24 -0500 (CDT)
Message-Id: <BCD14AB2-B275-420A-9AD5-278F1DFAD9AB@young-alumni.com>
From: Chris Ruiz <chris@young-alumni.com>
To: current@freebsd.org
In-Reply-To: <156527.19600.qm@web63901.mail.re1.yahoo.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 12 Mar 2009 16:17:22 -0500
References: <156527.19600.qm@web63901.mail.re1.yahoo.com>
X-Mailer: Apple Mail (2.930.3)
Cc: 
Subject: Re: Interrupt routine usage not shown by top in 8.0
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 21:36:56 -0000


On Mar 12, 2009, at 3:23 PM, Barney Cordoba wrote:

>
> I'm fireing 400Kpps at a udp blackhole port. I'm getting 6000  
> interrupts
> per second on em3:
>
> testbox# vmstat -i; sleep 1; vmstat -i
> interrupt                          total       rate
> irq1: atkbd0                           1          0
> irq6: fdc0                             1          0
> irq17: uhci1+                       2226          9
> irq18: uhci2 ehci+                     9          0
> cpu0: timer                       470507       1993
> irq256: em0                          665          2
> irq259: em3                      1027684       4354
> cpu1: timer                       470272       1992
> cpu3: timer                       470273       1992
> cpu2: timer                       470273       1992
> Total                            2911911      12338
>
> interrupt                          total       rate
> irq1: atkbd0                           1          0
> irq6: fdc0                             1          0
> irq17: uhci1+                       2226          9
> irq18: uhci2 ehci+                     9          0
> cpu0: timer                       472513       1993
> irq256: em0                          668          2
> irq259: em3                      1033703       4361
> cpu1: timer                       472278       1992
> cpu3: timer                       472279       1992
> cpu2: timer                       472279       1992
> Total                            2925957      12345
>
>
> top -SH shows:
>
>  PID  STATE  C   TIME    CPU COMMAND
>   10  CPU3   3   7:32 100.00% idle
>   10  CPU2   2   7:32 100.00% idle
>   10  RUN    0   7:31 100.00% idle
>   10  CPU1   1   7:31 100.00% idle
>
> This implies that CPU usage is substantially under-reported in general
> by the system. Note that I've modified em_irq_fast() to call
> em_handle_rxtx() directly rather than scheduling a task to illustrate
> the problem
>
> Barney

The version of top in the base system is known to provide incorrect  
metrics.

Chris