Date: Tue, 27 Jul 2010 08:46:03 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Alexander Motin <mav@FreeBSD.org> Cc: freebsd-geom@FreeBSD.org Subject: Re: Hyperactive g_event thread Message-ID: <24822.1280220363@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 27 Jul 2010 10:58:20 %2B0300." <4C4E919C.2060009@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <4C4E919C.2060009@FreeBSD.org>, Alexander Motin writes: >The only reason for doing it I >see in imperfect locking of g_run_events() loop and respective >tsleep()/wakeup(). So timeout there may be needed for collection >potentially lost wakeup() events. Back when GEOM was written, the kernels SMP facilites were rather rudimentary and in a few cases downright buggy, so workarounds like that timeout were employed. They can hopefully safely be removed now. -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24822.1280220363>