From: "Phil Frisbie, Jr." <phil@hawksoft.com>
To: ssundaragopalan@hss.hns.com
Cc: 5qduh001@sneakemail.com, pthreads-win32@sources.redhat.com
Subject: Re: pthread_init_mutex problem
Date: Mon, 06 May 2002 20:53:00 -0000 [thread overview]
Message-ID: <3CD75008.FCC6E157@hawksoft.com> (raw)
In-Reply-To: <65256BB1.004E4265.00@sampark.hss.hns.com>
ssundaragopalan@hss.hns.com wrote:
>
> hi ppl,
> thnx for your valuble inputs. ..actually i have implmented critical
> section as a solution and it works fine...the CPU utilization has come down
> to 60% from 100%...
That is just bandaging your design problem...
> thnx & regds,
> srikanth
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com
next prev parent reply other threads:[~2002-05-07 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 7:16 ssundaragopalan
2002-05-06 20:53 ` Phil Frisbie, Jr. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 10:42 5qduh001
2002-05-04 10:01 Eli Ofenstein
2002-05-04 4:19 ssundaragopalan
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=3CD75008.FCC6E157@hawksoft.com \
--to=phil@hawksoft.com \
--cc=5qduh001@sneakemail.com \
--cc=pthreads-win32@sources.redhat.com \
--cc=ssundaragopalan@hss.hns.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).