Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 16 Apr 2001 11:08:48 -0400 From: Christopher Faylor To: Cygwin-developers Subject: Re: dll_entry [was Re: fork expert needed: (was .....]) Message-ID: <20010416110848.A15438@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: Cygwin-developers References: <20010413221222 DOT C5606 AT dothill DOT com> <006001c0c4af$179b79c0$0200a8c0 AT lifelesswks> <20010414223139 DOT A906 AT redhat DOT com> <001701c0c557$02a861b0$0200a8c0 AT lifelesswks> <20010415090600 DOT A8359 AT redhat DOT com> <001301c0c5af$9cb7e520$0200a8c0 AT lifelesswks> <20010415153317 DOT C9015 AT redhat DOT com> <013b01c0c613$53cdac00$0200a8c0 AT lifelesswks> <20010415222520 DOT E10309 AT redhat DOT com> <035e01c0c675$c2c11180$0200a8c0 AT voyager> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <035e01c0c675$c2c11180$0200a8c0@voyager>; from trevorforbes@ozemail.com.au on Mon, Apr 16, 2001 at 10:34:22PM +0930 On Mon, Apr 16, 2001 at 10:34:22PM +0930, Trevor Forbes wrote: >----- Original Message ----- >From: "Christopher Faylor" >> >> > Robert Collins wrote: >> >Also while MSDN states that only one thread at a time can call the >> >entry point function, it does not state or imply that other threads are >> >suspended during that process. >> >> Ok, I reluctantly stand corrected. I thought that both the MSDN and >> my own personal experience (waiting for a signal from Cygwi's signal >> thread that never arrived) said this. I couldn't find any reference >> to this, though. > >Moved thread location..... > >The system serializes calls to the dll entry point function and "it >suspends" the other related threads during the process. >(Jeffery Richer - Microsoft Press) > >The attached patch can avoid the bottleneck but it may introduce new/old >problems. What bottleneck are we eliminating? No one has mentioned a bottleneck. You seem to be fixing a non-problem. cgf