Date: Wed, 25 May 2005 11:54:27 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Matthias Buelow <mkb@incubus.de> Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Performance of 4.x vs 5.x (Re: Lifetime of FreeBSD branches) Message-ID: <20050525185427.GB92006@xor.obsecurity.org> In-Reply-To: <4294AB75.9080908@incubus.de> References: <84dead7205052420503fded0e9@mail.gmail.com> <4293FD27.90500@incubus.de> <20050525042706.GA60021@xor.obsecurity.org> <4294054C.9080207@incubus.de> <20050525050943.GA64320@xor.obsecurity.org> <42940A81.1030801@incubus.de> <20050525052214.GA76339@xor.obsecurity.org> <42940C87.5000705@incubus.de> <20050525053054.GA76491@xor.obsecurity.org> <4294AB75.9080908@incubus.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--DKU6Jbt7q3WqK7+M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 25, 2005 at 06:44:37PM +0200, Matthias Buelow wrote: > Kris Kennaway wrote: >=20 > >>interrupt total rate > >>irq1: atkbd0 586 0 > >>irq13: npx0 1 0 > >>irq14: ata0 94 0 > >>irq17: wi0 54 0 > >>irq20: fxp0 atapci1 62079 99 > >>irq21: uhci0 ehci0 1 0 > >>irq22: uhci1 1102 1 > >>lapic0: timer 1246549 1994 > >>lapic1: timer 1246427 1994 > >>Total 2556893 4091 > >>The only relevant conflict I could see is irc 20; but I had already=20 > >>tested that by removing fxp0 from the kernel. > > > >I wonder if USB is causing the problem all on its own..since that was > >the culprit in other situations when it was being triggered by virtue > >of interrupt sharing. Any chance you can try a non-USB mouse and > >remove USB from your kernel? >=20 > Ok, now USB (both uhci and ehci) is gone. The problem is still the=20 > same. vmstat -i: >=20 > interrupt total rate > irq1: atkbd0 1324 3 > irq12: psm0 8562 21 > irq13: npx0 1 0 > irq14: ata0 94 0 > irq17: wi0 381 0 > irq20: fxp0 atapci1 61956 154 > lapic0: timer 801433 1993 > lapic1: timer 801292 1993 > Total 1675043 4166 >=20 > To be frank, I do not believe it's got anything to do with locking or=20 > interrupts. It somehow seems just like the scheduler is doing a bad job= =20 > of balancing interactive processes vs. disk i/o. I've seen the same=20 > stuff for years on NetBSD (until they changed scheduling around 1.5 or=20 > so) and Linux (until 2.4 kernels). During that time FreeBSD didn't=20 > exhibit these symptoms and only in 5.x have I seen that kind of=20 > behaviour creep back in. Has the classic scheduler been changed=20 > somehow? Maybe I should try and see if the problem persists with the=20 > ULE scheduler? Others don't see this though, and in other cases it was *definitively proven* to be caused by the issue I mentioned. I'll have to think more about what to try next..thanks for running the tests. Kris --DKU6Jbt7q3WqK7+M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFClMnjWry0BWjoQKURAtwvAKDOueLRUxtwZrozws+j3MyidpK6nwCfabQj UJFjMCqWj1VBW4FjATHc9qA= =znEi -----END PGP SIGNATURE----- --DKU6Jbt7q3WqK7+M--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050525185427.GB92006>