Date: Mon, 16 Sep 2002 12:03:40 -0700 (PDT) From: Archie Cobbs <archie@dellroad.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Bruce Evans <bde@zeta.org.au>, Josef Karthauser <joe@FreeBSD.org>, "David O'Brien" <obrien@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_timeout.c Message-ID: <200209161903.g8GJ3e687116@arch20m.dellroad.org> In-Reply-To: <13645.1032171121@critter.freebsd.dk> "from Poul-Henning Kamp at Sep 16, 2002 12:12:01 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp writes: > >> > Sep 15 19:40:26 kernel: Expensive timeout(9) function: 0xc65dfc80(0xc659f000) 0.008711721 > >> > Sep 15 19:40:26 kernel: Expensive timeout(9) function: 0xc65dfc80(0xc659f000) 0.001068850 > > > >This is hard to interpret without the function names (or a full stack > >trace). > > Yes, but as far as I'm aware, we still don't have a print_backtrace(9) ? > > >I get these on an old dual Celeron system mainly for fxp_tick() > >and uma_timeout(). > > uma_timeout() seems to trigger on practically all systems. > I've talked with Jeff about it already. Would an option to timeout() like SPAWN_SEPARATE_THREAD be a practical solution for some of these cases? I.e., optionally spawn a separate thread to handle the timeout() event. This may be expensive, but there may also be some timeout events that are rare, slow and expensive enough themselves to warrant using it. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209161903.g8GJ3e687116>