From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 7 17:58:02 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8FEDE353 for ; Sat, 7 Jun 2014 17:58:02 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 317432321 for ; Sat, 7 Jun 2014 17:58:02 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id s57HvqWE021637; Sat, 7 Jun 2014 20:57:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua s57HvqWE021637 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.8/Submit) id s57HvqLA021636; Sat, 7 Jun 2014 20:57:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 7 Jun 2014 20:57:52 +0300 From: Konstantin Belousov To: Dutch Ingraham Subject: Re: Fwd: Interrupt Overload Message-ID: <20140607175752.GP3991@kib.kiev.ua> 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> <53934250.1090403@gmx.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SlNsYPPA1sYaSN7W" Content-Disposition: inline In-Reply-To: <53934250.1090403@gmx.us> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-hackers@freebsd.org 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 17:58:02 -0000 --SlNsYPPA1sYaSN7W Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 07, 2014 at 12:48:16PM -0400, Dutch Ingraham wrote: > On 06/07/2014 12:04 PM, Vladislav Prodan wrote: > >=20 > >=20 > > =20 > > --- Original message --- > > From: "Dutch Ingraham" > > Date: 7 June 2014, 18:33:12 > > =20 > >=20 > >> > >> 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. > >=20 > > After reboot what became timer? :) > >=20 > > You can change the timer "on the fly", without rebooting the system. > >=20 > > If LAPIC does not help, then try other timers. > >=20 > >=20 > > -- > > Vladislav V. Prodan > > System & Network Administrator > > support.od.ua > > =20 > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" > >=20 >=20 > 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. >=20 > 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? You did not shown _useful_ output of vmstat -i. Do it when the storm occurs. Also, show the pciconf -lvc output on the machine. --SlNsYPPA1sYaSN7W Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJTk1KfAAoJEJDCuSvBvK1B18UP+wWcdB8DAcwXxD+P7pdUG5Ql 5IFRioTm/4T9dgb3/zSVy2i66L5mAY+bIDGC7HOUVffyfkZDC1dzzpKSdE3lIJmm 7YvEV+luXURfOUnj1cvrdmJ91ld4jY0CMBgUvb1EJzylQr080H1Lxfg7KPPVL+Go XtVgf+l8e8/0MIC3ovZK2Vb9k5YPvP5GIR2Ep+FGac8Zl0XaJ9KTKB4DFgAu1DXq R9nyTsyHfWg+T4+ongV39SAZmJXvvO0al10wOWNSCembhabaFI1A7B/YwL3l3MOr yAvHeTaDeJoLHe0Lok7a9FCKTqCmw+3Q8zIxts7iDHXsXbehdTLubBcfF9zboo5t M5eJ8gYAo01oGX1hkW7n68n5wHwzj8AkgSUk9lVy8zpnz5HEuydz6AK0CFUeEJs7 hlOtcpacBXbMmYuaq8YP1LwfLpkCvWZ4FejUf6+bTdDOr5tJHNeDckKMw4ejJ5O2 QW2gI7IMK+LjZxeBFTJoizQcLs5/Rul5SyuetK+wGLY4HA0s0/X2QY5tBpxRvjeI an0cNz/vMMCmvS6POXY+HOgWeDOugnrJxr9lbMNarEaZ4qV8pldA+UyRQQHhQTKM MlwAI7R4VT8sKBOctoKfn3Unf8W5g8uTE5Lm6Yi2jFUfc0nJ0vuiriS37eDVBiQf A1vlp8oNYZvPQEdjNw2r =IdXS -----END PGP SIGNATURE----- --SlNsYPPA1sYaSN7W--