Date: Mon, 16 Sep 2002 21:20:14 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Archie Cobbs <archie@dellroad.org> 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: <84439.1032204014@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 16 Sep 2002 12:03:40 PDT." <200209161903.g8GJ3e687116@arch20m.dellroad.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200209161903.g8GJ3e687116@arch20m.dellroad.org>, Archie Cobbs write s: >> 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. I'm not sure, this (or anything else) is the way to go. I have wondered if periodic events should be handled differently, or at least separately from one-shots, but that is also just an idea. I think what we need more than anything, is somebody gathering more hard data and analyzing more... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?84439.1032204014>