From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27450 invoked by alias); 4 May 2002 07:09:02 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 27416 invoked from network); 4 May 2002 07:09:01 -0000 Received: from unknown (HELO hss.hns.com) (164.164.94.118) by sources.redhat.com with SMTP; 4 May 2002 07:09:01 -0000 Received: from sampark.hss.hns.com (hssblrmail [192.168.17.10]) by hss.hns.com (8.11.6/8.11.2) with SMTP id g4477tH09752 for ; Sat, 4 May 2002 12:37:55 +0530 Received: by sampark.hss.hns.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 65256BAF.00273C65 ; Sat, 4 May 2002 12:38:33 +0530 X-Lotus-FromDomain: HSSBLR From: ssundaragopalan@hss.hns.com To: pthreads-win32@sources.redhat.com Message-ID: <65256BAF.00273A7F.00@sampark.hss.hns.com> Date: Sat, 04 May 2002 00:09:00 -0000 Subject: pthread_init_mutex problem Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-SW-Source: 2002/txt/msg00055.txt.bz2 hi all, i am new to this mailing list. i am using pthreads for windows and have the following problems. The function pthread_mutex_init is taking up CPU to a large extent....In our program we have a lock for each data structure and this data struture is initialized every time a new messsage is received. So under Load conditions the CPU utilization is reaching 100%. Can anyone suggest some ways to bring down this. regds, srikanth This message is proprietary to Hughes Software Systems Limited (HSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. HSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.