Date: Sun, 10 Apr 2005 00:04:21 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 537 ************************************************** Saturday 09 April 2005 Number 537 ************************************************** Subjects for today 1 Re: Python 2.4.1 EMX port released. : Steven Levine" **= Email 1 ==========================** Date: Fri, 08 Apr 2005 07:59:53 -0700 From: "Steven Levine" Subject: Re: Python 2.4.1 EMX port released. In <1112953261.425651adc2677 at modem.webmail.t-online.de>, on 04/08/05 at 11:51 AM, Stefan.Neis at t-online.de said: >Not sure what you mean by a "configuration variable", I mean something stored in an application specific configuration profile. For example, the latest 2.x versions of Apache add support for a ThreadStackSize configuration parameter which lives in httpd.conf. Unfortunately, this is not yet supported by the OS/2 port. >That way, all programs wanting to support configurable thread stack size >would still need to be slightly modified and recompiled, but that >shouldn't be a big problem. This is pretty much the way I would expect it to be implemented. >Of course, thread creation is probably protected by a mutex, so anything >increasing the time during which the mutex is >locked is probably bad, but I hope that looking up an >environment variable is not going to take long enough to >cause a real problem. I would arrage to do the checks only once outside any mutex as in: if stackSizeKnown not known determine preferred stack size set stackSizeKnown endif create thread I don't think there's any benefit to doing a full check for every thread created. Regards, Steven -- ---------------------------------------------------------------------- "Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) ----------------------------------------------------------------------