Date: Wed, 11 Feb 2004 09:30:29 +0800 From: David Xu <davidxu@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: freebsd-threads@freebsd.org Subject: Re: Question about threads [beaver challenge] Message-ID: <402985B5.8080703@freebsd.org> In-Reply-To: <Pine.BSF.4.21.0402101716170.82714-100000@InterJet.elischer.org> References: <Pine.BSF.4.21.0402101716170.82714-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: >>>process scope threads a re perfectly reasonable.. they however >>>use more resources and are more heavily limitted. >>> >>> >>>On the other hand process scope threads can lead to nasty surprises with >>>the limits as they can "suddenly" hit th ekernel limit after running >>>successfully for a time when they all (by some fluke) all decide to >>>enter the kernel at the same time. >>> >>> >>Well, since the kernel limit for scope system threads is much smaller >>than that for "threads blocked in kernel", you'd hit the limit much >>sooner if the port/application used scope system threads instead >>of scope process threads. >> >> > >but at least it wouldn't be a surprise :-) > You can print a warning message like LDT allocating code. David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?402985B5.8080703>