X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: In-Reply-To: <4C0933BD.2060701@redhat.com> References: <4C03D6C5 DOT 4050004 AT x-ray DOT at> <80373222dd5d43b134a5ede7036e7674 DOT squirrel AT www DOT webmail DOT wingert DOT org> <20100602080626 DOT GV16885 AT calimero DOT vinschen DOT de> <383c8b44a088dad09a0b77d3299feda7 DOT squirrel AT www DOT webmail DOT wingert DOT org> <20100602174848 DOT GA14172 AT ednor DOT casa DOT cgf DOT cx> <20100603235944 DOT GA12167 AT ednor DOT casa DOT cgf DOT cx> <20100604024422 DOT GB12167 AT ednor DOT casa DOT cgf DOT cx> <78e7b77657c0cfcd63dc22ad9679bc85 DOT squirrel AT www DOT webmail DOT wingert DOT org> <20100604045807 DOT GC12167 AT ednor DOT casa DOT cgf DOT cx> <2570318aabfa537bf24c8d3a55f9dcd4 DOT squirrel AT www DOT webmail DOT wingert DOT org> <4C092F96 DOT 5040800 AT cygwin DOT com> <7a1785a5f0a1d0a8956cd10e573f2e53 DOT squirrel AT www DOT webmail DOT wingert DOT org> <4C0933BD DOT 2060701 AT redhat DOT com> Date: Fri, 4 Jun 2010 10:33:47 -0700 Subject: Re: Cygwin Performance and stat() From: "Christopher Wingert" To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.4.20 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > [quit top-posting] Now you are my mom too? > That's where you're wrong. Any patch you write that is technically > sound and shows a measurable improvement will most likely be accepted. Then you shouldn't have Cygwin's front line technical spokesman saying things such as: "If there was a way to make stat() faster why wouldn't it be in the source code already?" "Otherwise, I doubt that anyone outside of the cygwin developers understands the stat() code well enough to come up with a patch." "But providing a variant of stat() along the lines of what you propose above is not practical for all the reasons already stated." "I guess it's possible that someone just doesn't want to go through the pain of getting the patch accepted. In that case, everyone enjoy your private cygwin stat() patches." ------------ When I threw the idea out initially I asked for input from the people that have more experience in Cygwin than I do. I have been seeing these performance issues for years of using Cygwin. However, in the past week had some time to look at it. FWIW, because of the initial resistance I have been shown by the "front line developers." I have already contemplated of my own Cygwin branch. All that being said, I think the best solution is not to optimize the dll stat(), but to do it at the executable level. I see that Cygwin already has some level of patches at this level, it shouldn't be too difficult to support. Chris -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple