Date: Fri, 6 Feb 2004 15:00:40 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: Daniel Eischen <eischen@vigrid.com> Cc: current@FreeBSD.org Subject: Re: python ports broken (sem_destroy: Resource temporarily Message-ID: <Pine.BSF.4.21.0402061458450.24800-100000@InterJet.elischer.org> In-Reply-To: <Pine.GSO.4.10.10402061626330.24638-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Feb 2004, Daniel Eischen wrote: > > > > Why? > > System scope threads each have their own KSEG/KSE pair. > The default thread limits in the kernel are: > > kern.threads.max_threads_per_proc: 150 > kern.threads.max_groups_per_proc: 50 > > By default there are 2 KSEGs for a threaded process in > libpthread: one for scope process threads and one for > the signal handling thread. That leaves 48 for left for > application use. > > Those limits are arbitrary, so you can raise/lower them > if you don't like them. I thought you came up with those > limits ;-) I know all that :-) Why do they make system scope threads? :-) couldn't part of a freebsd port patch be to make them process scoe threads.. it'd be more efficient.. > > -- > Dan Eischen > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0402061458450.24800-100000>