Hyperactive g_event thread

[Poul-Henning Kamp]

In message <4C4E919C.2060009 at 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 at 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.