X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0EC96384A033 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1597902044; bh=x2BKdBlpvnewIKVeOXzAEceHYZ9fENmtawpgxHcc9Jw=; h=Subject:To:Date:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=IjHI7tRK1ZrvOcTxhEAb1PkRLLoL8fPqS1ApV3mSwvY83OuGb6H5VNfypuqh3P7Lx VrAWzygt0uPz0ZttXF8pqxuSTlC8ypggUjF+E4B2ppBPrmDrnH0xORsFk+BqW8i9pU Lne4InLoAff3ZcnqkjiPyNXi/pnZCvTZ2wPs2jDs= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 075BE3864877 Message-ID: <1ae8de15bb74efb7207299d2dba92cdef88d9a94.camel@tdcadsl.dk> Subject: Re: Synchronization problem with posix_spawn To: cygwin AT cygwin DOT com Date: Thu, 20 Aug 2020 07:40:37 +0200 In-Reply-To: <20200803105004.GK460314@calimero.vinschen.de> References: <864b3031-9fc8-beb3-ba7c-1ade4c31a288 AT cornell DOT edu> <20200730115913 DOT GL4206 AT calimero DOT vinschen DOT de> <20200730171723 DOT GA460314 AT calimero DOT vinschen DOT de> <86051625-646d-065a-8543-1c3086411d3d AT cornell DOT edu> <20200731081025 DOT GB460314 AT calimero DOT vinschen DOT de> <9c44f4351d459a2ba8d27c65bf71679208cb13d6 DOT camel AT tdcadsl DOT dk> <20200803105004 DOT GK460314 AT calimero DOT vinschen DOT de> User-Agent: Evolution 3.36.4 (3.36.4-1.fc32) MIME-Version: 1.0 X-yse-mailing: LEGIT X-yse-spamcause: OK, (0)(0000)gggruggvucftvghtrhhoucdtuddrgeduiedruddtledgjeekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvfffvedpggftfgfpufgfuefuveftkfeugfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefkuffhvfffjghftggfggfgsehtjeertddtreejnecuhfhrohhmpefrvghtvghrucffohhnshcuvfihtghhshgvnhcuoeguohhnphgvughrohesthgutggrughslhdrughkqeenucggtffrrghtthgvrhhnpedtiefggeeuudevkedvgeefueefiefhgeelvdekveeiieehffeitdekueeitdejffenucfkphepleegrddugeejrdeitddrfedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplhhotggrlhhhohhsthdrlhhotggrlhguohhmrghinhdpihhnvghtpeelgedrudegjedriedtrdeftddpmhgrihhlfhhrohhmpeguohhnphgvughrohesthgutggrughslhdrughkpdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomh X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Peter Dons Tychsen via Cygwin Reply-To: Peter Dons Tychsen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Hi Corinna, > spawn alone doesn't cut it, due to the requirement to support the > additional file actions and spawn atributes POSIX defines. This > would require a revamp of Cygwin's spawn functionality, which is > already quite complicated. So this is something I'm only willing > to do in homeopathic doses. OK. I can see that most of the processing of the options are done seperately. We could to start with create a shortcut that calls spawn[vpe]() instead if there are no options specified? That would speed up most cases. Then we could add the extra cases later if needed. Would that be an acceptable patch? The reason i am pushing for this is that allot of developers i interact with get the feeling cygwin is slow. When i look into their cases it is almost always because they use programs that end up calling fork() allot (large shell scripts, makefiles, etc.). Almost all modern versions of these programs have support for calling posix_spawn() instead when creating processes, which would (if we changed it) speed up these cases dramatically if it avoided fork(). It would simply make cygwin more appealing to this group of users. Thanks, /pedro -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple