From owner-freebsd-net@FreeBSD.ORG  Mon Jul 26 15:01:03 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7F15616A4CE
	for <freebsd-net@freebsd.org>; Mon, 26 Jul 2004 15:01:03 +0000 (GMT)
Received: from mx01.bos.ma.towardex.com (mx01.bos.ma.towardex.com
	[65.124.16.9])	by mx1.FreeBSD.org (Postfix) with ESMTP id 52D3243D31
	for <freebsd-net@freebsd.org>; Mon, 26 Jul 2004 15:01:03 +0000 (GMT)
	(envelope-from haesu@mx01.bos.ma.towardex.com)
Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid
	1001)	id 1213D2F964; Mon, 26 Jul 2004 11:01:03 -0400 (EDT)
Date: Mon, 26 Jul 2004 11:01:03 -0400
From: James <haesu@towardex.com>
To: Don Bowman <don@sandvine.com>
Message-ID: <20040726150103.GA26080@scylla.towardex.com>
References: <FE045D4D9F7AED4CBFF1B3B813C85337051D9433@mail.sandvine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C85337051D9433@mail.sandvine.com>
User-Agent: Mutt/1.4.1i
cc: freebsd-net@freebsd.org
Subject: Re: device polling takes more CPU hits??
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2004 15:01:03 -0000

Hi Don,

> I would post the output of 'sysctl kern.polling', its likely
> some of the tuning there is insufficient.
> What do you have HZ set to (sysctl kern.clockrate)? I would
> probably have it set to ~1000.
> You will want 'machdep.cpu_idle_hlt=1'.

Thanks for quick reply. Here is the sysctl output with polling turned on.

-J

root@r2.bos# sysctl kern.clockrate
kern.clockrate: { hz = 4000, tick = 250, tickadj = 1, profhz = 1024, stathz = 128 }
        
root@r2.bos# sysctl kern.polling
kern.polling.burst: 150
kern.polling.each_burst: 5
kern.polling.burst_max: 150
kern.polling.idle_poll: 1
kern.polling.poll_in_trap: 1
kern.polling.user_frac: 50
kern.polling.reg_frac: 20
kern.polling.short_ticks: 4909
kern.polling.lost_polls: 11464
kern.polling.pending_polls: 0
kern.polling.residual_burst: 0
kern.polling.handlers: 1
kern.polling.enable: 1
kern.polling.phase: 0
kern.polling.suspect: 10249
kern.polling.stalled: 3
                                                                                root@r2.bos# sysctl machdep.cpu_idle_hlt
machdep.cpu_idle_hlt: 1


-- 
James Jun                                            TowardEX Technologies, Inc.
Technical Lead                        Network Design, Consulting, IT Outsourcing
james@towardex.com                  Boston-based Colocation & Bandwidth Services
cell: 1(978)-394-2867           web: http://www.towardex.com , noc: www.twdx.net