X-Spam-Check-By: sourceware.org Message-ID: <455BD867.8090702@cwilson.fastmail.fm> Date: Wed, 15 Nov 2006 22:17:59 -0500 From: Charles Wilson User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Excessive thrashing when popen()ing after a large malloc() References: <4559D376.9030707@byu.net> <20061115165133.GA21115@trixie.casa.cgf.cx> In-Reply-To: <20061115165133.GA21115@trixie.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Christopher Faylor wrote: > Fully implementing posix_spawn is quite a bit of work although I did > tell Linus Torvalds that I'd look into implementing it in Cygwin > eventually (it would make git-on-cygwin faster). > > I have a patch in my sandbox which implements a more lightweight > approach for popen using cygwin internals. Don't you go thru this exercise about every two years? 1) fork/exec implementation in cygwin sux 2) attempt to rewrite cygwin internals to use symantics of spawn|vfork|some-other-clever-idea 3) it breaks a bunch of stuff 4) try to patch around the problems, repeat #3 4) revert back to original fork/exec implementation What's different this time? (Really, I'm not being snarky, and maybe I'm misremembering, but I'd hate to see precious developer time spent in #2 thru #4 if #5 will happen anyway -- if the past is any guide.) -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/