This is the mail archive of the
mailing list for the pthreas-win32 project.
RE: pthread_init_mutex problem
- From: Eli Ofenstein <elio at clearcommerce dot com>
- To: "'ssundaragopalan at hss dot hns dot com'" <ssundaragopalan at hss dot hns dot com>, pthreads-win32 at sources dot redhat dot com
- Date: Sat, 4 May 2002 12:01:38 -0500
- Subject: RE: pthread_init_mutex problem
In general, sync primitives as data structures aren't really meant to be
transient. A high cost at init time is not uncommon. In terms of
protecting data that is transient, perhaps a scheme for reusing the
data structures would be in order. Something like maintaining a linklist,
or, even better, per-thread linklists on a TLS key. Of course, this assumes
near-identical produce and consume rates.
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org]
> Sent: Saturday, May 04, 2002 2:08 AM
> To: email@example.com
> Subject: pthread_init_mutex problem
> 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
> 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.
> 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
> 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.