01-19-2005
10 More Discussions You Might Find Interesting
1. Programming
I am trying to find out that how many number of threads are currently running or in any other state which is created by POSIX standard in a process.
First I have defined a variable called proc_var of type proc defined in sys/proc.h.Next I open up the dir /proc and per directory wise I do an ioctl... (7 Replies)
Discussion started by: S.P.Prasad
7 Replies
2. UNIX for Advanced & Expert Users
Hi,
Can someone tell help me on how to know the threads statistics on a unix machine similar to memory statisitcs.
I woule like to monitor the Number of threads per process and total number of threads that a system can accomodate.
Thank you
mrag (1 Reply)
Discussion started by: mrag74
1 Replies
3. Linux
Hi
Anybody knows max. no. of threads handled by a process in linux. Please reply
Thanks in advnce :confused: (0 Replies)
Discussion started by: Agnello
0 Replies
4. UNIX for Advanced & Expert Users
Hi all,
How can I get the list of all Threads and the Total count of threads under a particular process ?
Do suggest !!
Awaiting for the replies !!
Thanks
Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies
5. Programming
Hi,
I am stuck up with a strange problem.
I am writing an application - a kinda tracker that reads data from memcache and invokes theads to process each record of the memcache.
I dont want to join all my threads because my tracker should poll the cache in regular intervals say sum 300... (2 Replies)
Discussion started by: deepti_v25
2 Replies
6. UNIX for Advanced & Expert Users
What are the maximum number of threads possible per Process? Is it OS dependent? (1 Reply)
Discussion started by: digdarshan
1 Replies
7. Programming
I am writing java application on windows.
There are more than 100 threads run within java.exe.
I want to know what threads run within process java.exe so that I can find out if there are abnormal java threads. (4 Replies)
Discussion started by: mika
4 Replies
8. AIX
Hello,
On Linux, I can use 'ps -efL | grep process_name' to list all threads that belong to a running process. -L has a different meaning on AIX and I could not find an equivalent flag in the man pages.
Does anyone know of a way to dump the threads under a running process?
Thanks,... (2 Replies)
Discussion started by: makodarear
2 Replies
9. UNIX for Advanced & Expert Users
I would like to know is there any we can kill a single thread among multiple threads belongs to process?
Since Signal action is process wise not per thread, i strongly feel that we can not or for that mater from external sources as well single thread can not be killed which is critical section... (2 Replies)
Discussion started by: murali242512
2 Replies
10. HP-UX
Hi All,
When i was trying to get total number of threads per java process using this command ps -o NLWP PID, I'm not getting any output. Could someone help me in this issue.
Thanks,
GMar (1 Reply)
Discussion started by: mgangumolu
1 Replies
LEARN ABOUT FREEBSD
pthread_barrier_wait
PTHREAD_BARRIER(3) BSD Library Functions Manual PTHREAD_BARRIER(3)
NAME
pthread_barrier_destroy, pthread_barrier_init, pthread_barrier_wait -- destroy, initialize or wait on a barrier object
LIBRARY
POSIX Threads Library (libpthread, -lpthread)
SYNOPSIS
#include <pthread.h>
int
pthread_barrier_destroy(pthread_barrier_t *barrier);
int
pthread_barrier_init(pthread_barrier_t *barrier, const pthread_barrierattr_t *attr, unsigned count);
int
pthread_barrier_wait(pthread_barrier_t *barrier);
DESCRIPTION
The pthread_barrier_init() function will initialize barrier with attributes specified in attr, or if it is NULL, with default attributes.
The number of threads that must call pthread_barrier_wait() before any of the waiting threads can be released is specified by count. The
pthread_barrier_destroy() function will destroy barrier and release any resources that may have been allocated on its behalf.
The pthread_barrier_wait() function will synchronize calling threads at barrier. The threads will be blocked from making further progress
until a sufficient number of threads calls this function. The number of threads that must call it before any of them will be released is
determined by the count argument to pthread_barrier_init(). Once the threads have been released the barrier will be reset.
IMPLEMENTATION NOTES
In both N:M Threading Library (libkse, -lkse) and 1:1 Threading Library (libthr, -lthr) the PTHREAD_BARRIER_SERIAL_THREAD return value will
always be returned by the last thread to reach the barrier.
RETURN VALUES
If successful, both pthread_barrier_destroy() and pthread_barrier_init() will return zero. Otherwise, an error number will be returned to
indicate the error. If the call to pthread_barrier_wait() is successful, all but one of the threads will return zero. That one thread will
return PTHREAD_BARRIER_SERIAL_THREAD. Otherwise, an error number will be returned to indicate the error.
None of these functions will return EINTR.
ERRORS
The pthread_barrier_destroy() function will fail if:
[EBUSY] An attempt was made to destroy barrier while it was in use.
The pthread_barrier_destroy() and pthread_barrier_wait() functions may fail if:
[EINVAL] The value specified by barrier is invalid.
The pthread_barrier_init() function will fail if:
[EAGAIN] The system lacks resources, other than memory, to initialize barrier.
[EINVAL] The count argument is less than 1.
[ENOMEM] Insufficient memory to initialize barrier.
SEE ALSO
pthread_barrierattr(3)
HISTORY
The pthread_barrier_destroy(), pthread_barrier_init() and pthread_barrier_wait() functions first appeared in N:M Threading Library (libkse,
-lkse) in FreeBSD 5.2, and in 1:1 Threading Library (libthr, -lthr) in FreeBSD 5.3.
BSD
February 19, 2004 BSD