From: ssundaragopalan@hss.hns.com
To: pankaj bathwal <pbathwal@yahoo.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: pthread_init_mutex problem
Date: Sat, 04 May 2002 04:19:00 -0000 [thread overview]
Message-ID: <65256BAF.003E1EF2.00@sampark.hss.hns.com> (raw)
hi pankaj,
thnx for your Input...i found that your code was not taking much of
CPU after introducing a sleep for once mili sec.
i have a different scene here..i have multiple threads trying to do the
same operations as what your main does.
Please have a look at this and give me your suggestions
#include "pthread.h"
#include <assert.h>
int main()
{
CreateThread(NULL,0,mythread1,"Thread1",0,&thrId1);
CreateThread(NULL,0,mythread1,"Thread2",0,&thrId2);
for(;;)
{
Sleep(1);
}
return 0;
}
DWORD WINAPI mythread1(void*ptr)
{
int i=0;
for(i = 0; i != 1000000; i++)
{
pthread_mutex_t mutex;
assert(pthread_mutex_init(&mutex, NULL) == 0);
assert(mutex != NULL);
assert(pthread_mutex_lock(&mutex) == 0);
printf("Locked:%s\n",(char*)ptr);
Sleep(1);
assert(pthread_mutex_unlock(&mutex) == 0);
printf("UnLocked\n");
assert(pthread_mutex_destroy(&mutex)==0);
printf("Destroy\n");
}
}
regds & thnx
srikanth
pankaj bathwal <pbathwal@yahoo.com> on 05/04/2002 10:53:46 AM
To: Srikanth Sundaragopalan/HSSBLR
cc:
Subject: Re: pthread_init_mutex problem
hi,
i think problem is not in the pthread_mutex_init
i have tried the below code and cpu never goes above
15%.....
Use debugger to find if problem is really in the
pthread_mutex_init
#include "pthread.h"
#include <assert.h>
int main()
{
for(int i = 0; i != 100; i++)
{
pthread_mutex_t mutex;
assert(pthread_mutex_init(&mutex, NULL) == 0);
assert(mutex != NULL);
assert(pthread_mutex_lock(&mutex) == 0);
assert(pthread_mutex_unlock(&mutex) == 0);
}
return 0;
}
cheers
pankaj
--- ssundaragopalan@hss.hns.com wrote:
>
>
> 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.
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
next reply other threads:[~2002-05-04 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 4:19 ssundaragopalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-06 7:16 ssundaragopalan
2002-05-06 20:53 ` Phil Frisbie, Jr.
2002-05-04 10:42 5qduh001
2002-05-04 10:01 Eli Ofenstein
2002-05-04 0:09 ssundaragopalan
2002-05-04 11:28 ` Phil Frisbie, Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65256BAF.003E1EF2.00@sampark.hss.hns.com \
--to=ssundaragopalan@hss.hns.com \
--cc=pbathwal@yahoo.com \
--cc=pthreads-win32@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).