From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 7 16:46:42 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66E0490A for ; Sat, 7 Jun 2014 16:46:42 +0000 (UTC) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 300B12D6E for ; Sat, 7 Jun 2014 16:46:42 +0000 (UTC) Received: from [192.168.1.68] ([172.15.184.248]) by mail.gmx.com (mrgmxus001) with ESMTPSA (Nemesis) id 0LeMmZ-1WRkEe00Nh-00qCb7 for ; Sat, 07 Jun 2014 18:46:41 +0200 Message-ID: <53934250.1090403@gmx.us> Date: Sat, 07 Jun 2014 12:48:16 -0400 From: Dutch Ingraham User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Fwd: Interrupt Overload References: <538A3432.5010303@gmx.us> <53930E19.8090603@gmx.us> <53931963.4040604@selasky.org> <53932314.6010108@gmx.us> <1402153691.709851721.u6k6kkkk@frv35.fwdcdn.com> <53933110.8060300@gmx.us> <1402157083.156846225.m95e69ke@frv35.fwdcdn.com> In-Reply-To: <1402157083.156846225.m95e69ke@frv35.fwdcdn.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:QjYlB4XFC8e6qLPr5IkPoFyrNXD91JHHQVBoJorHHtJa6n4ncXm J6Zm1KWwcJsRQfYqVtf6NWdRmystYu2cwSAC9U5A2emFNf2bt7eCuIjHVfEAWvIPvvK3SXb tvykfwtLUeWgKCXNToI8ce/n+houg3h7aVTGrc3VY9OhzvCLXqmj7ST56PEUSToH4Y1ZpR6 /FUzB+UPOzTYMOqlEWzsw== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2014 16:46:42 -0000 On 06/07/2014 12:04 PM, Vladislav Prodan wrote: > > > > --- Original message --- > From: "Dutch Ingraham" > Date: 7 June 2014, 18:33:12 > > >> >> Thanks for the response. >> >> The output you requested: >> >> kern.eventtimer.choice: HPET1 (440) HPET2 (440) HPET3 (440) HPET4 (440) >> HPET5 (440) HPET6 (440) LAPIC (400) i8254 (100) RTC (0) >> >> kern.eventtimer.choice: HPET (did not specify 1, 2, etc.) >> >> I also changed the type of timer to LAPIC and rebooted; there was no >> appreciable change in the interrupt activity. > > After reboot what became timer? :) > > You can change the timer "on the fly", without rebooting the system. > > If LAPIC does not help, then try other timers. > > > -- > Vladislav V. Prodan > System & Network Administrator > support.od.ua > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > You're right, it is not persistent. I changed to each different event timer and the only one that made a difference was the i8254; that dropped the cpu load from 30% to 10-12%. Much better, but still of course not acceptable for a Core II-Duo running at 3.0GHz. The load averages shown in do also drop proportionally. Interestingly, though, shows the same interrupt rate - 325K/sec. What do you make of the fact that when I suspend with < and then wake-up, everything is absolutely normal, regardless of event timer type?