Date: Thu, 1 Jun 2006 08:27:47 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, Scott Long <scottl@samsco.org>, src-committers@FreeBSD.org, Warner Losh <imp@FreeBSD.org>, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/syscons/apm apm_saver.c src/sys/i386/bios apm.c apm.h Message-ID: <20060601042747.GX27819@FreeBSD.org> In-Reply-To: <200605311123.02334.jhb@freebsd.org> References: <200605252306.k4PN6cCS081708@repoman.freebsd.org> <200605311050.12156.jhb@freebsd.org> <447DAF19.3050901@samsco.org> <200605311123.02334.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 31, 2006 at 11:23:01AM -0400, John Baldwin wrote: J> Nah, that was phk's other timekeeping code to see which timeouts take a long J> time to execute. The THREAD_NO_SLEEPING() stuff was added just before 6.0 J> was released and replaced a couple of "special" mutexes that were held just J> to provoke WITNESS warnings. To take a long time to execute one doesn't need to sleep, it can also do a lot of job. I know at least two examples of heavy callouts: dummynet and pf. Under heavy traffic both subsystems process a lot of packets during one callout. I have patches to move their job to a separate taskqueue. The dummynet patch needs some testing and the pf patch waits for Max Laier to decide what to chose: taskqueue API or kthread_create() as newest pf in OpenBSD does. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060601042747.GX27819>