From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9423 invoked by alias); 6 Sep 2010 11:32:56 -0000 Received: (qmail 9415 invoked by uid 22791); 6 Sep 2010 11:32:55 -0000 X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SARE_RECV_IP_080178 X-Spam-Check-By: sourceware.org Received: from mail-ew0-f43.google.com (HELO mail-ew0-f43.google.com) (209.85.215.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 06 Sep 2010 11:32:23 +0000 Received: by ewy1 with SMTP id 1so3008130ewy.2 for ; Mon, 06 Sep 2010 04:32:21 -0700 (PDT) Received: by 10.213.34.83 with SMTP id k19mr694197ebd.34.1283772740768; Mon, 06 Sep 2010 04:32:20 -0700 (PDT) Received: from [192.168.88.50] (doors.graphtech.co.il [80.179.212.100]) by mx.google.com with ESMTPS id v59sm7929041eeh.4.2010.09.06.04.32.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 06 Sep 2010 04:32:19 -0700 (PDT) Message-ID: <4C84D12A.2080506@graphtech.co.il> Date: Mon, 06 Sep 2010 11:32:00 -0000 From: Sagi Ben-Akiva User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100714 SUSE/2.0.6-3.1 SeaMonkey/2.0.6 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Cygwin slow on x64 systems References: <4C7B9327.9030204@graphtech.co.il> <4C7E8A40.4090102@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2010-09/txt/msg00203.txt.bz2 Hi Magnus, I applied your patch but I don't notice for any improvement in performance with my test case (I still get only 7 lines/sec). I tried it with several cygwin 1.7.7-1 revisions Which version of cygwin sources do you use ? Did you try it with the latest snapshot ? Thanks, Sagi. Magnus Holmgren wrote: >>>> I did some testing on my 64-bit Vista system, and it appears that >>>> CreateThread is the main cause. >>> >>> To test this, I removed the call to sigproc_init in dll_crt0_0 and made sure >>> it was always called in dll_crt0_1 instead. Suddenly the sigp thread started >>> executing immediately, and its initialization was complete long before >>> wait_for_sigthread was called. >> >> Since you obviously have a patch, would you mind sharing it, rather than >> just your conclusions from said patch? > > Not quite ready for commit as is, but here it is: > > Index: src/winsup/cygwin/dcrt0.cc > =================================================================== > RCS file: /cvs/src/src/winsup/cygwin/dcrt0.cc,v > retrieving revision 1.382 > diff -r1.382 dcrt0.cc > 746,747c746,747 > < if (!dynamically_loaded) > < sigproc_init (); > --- >> //if (!dynamically_loaded) >> //sigproc_init (); > 792c792 > < if (dynamically_loaded) > --- >> //if (dynamically_loaded) > > Magnus > -- 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