thread count using top


 
Thread Tools Search this Thread
Operating Systems Solaris thread count using top
# 1  
Old 03-14-2006
thread count using top

I am running a multithreaded program which creates 10 threads and works away.

However, when I use top to monitor my program whilst it is running, it only shows 4 under the thread count!

Can anyone explain if this is in fact the number of threads running in my process...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Thread count for a process id

Hi, I want to know a command/program to get thread count for a process id in unix box. Please help me in this regard. (1 Reply)
Discussion started by: manaac
1 Replies

2. AIX

Need a list of top 10 CPU using processes (also top 10 memory hogs, separately)

Okay, I am trying to come up with a multi-platform script to report top ten CPU and memory hog processes, which will be run by our enterprise monitoring application as an auto-action item when the CPU and Memory utilization gets reported as higher than a certain threshold I use top on other... (5 Replies)
Discussion started by: thenomad
5 Replies

3. AIX

Top command in AIX 4.2 (no topas, no nmon, no top)?

Is there a 'top' command equivalent in AIX 4.2 ? I already checked and I do not see the following ones anywhere: top nmon topas (1 Reply)
Discussion started by: Browser_ice
1 Replies

4. Shell Programming and Scripting

thread count

Hi, I have a log file in which there are plenty of threads. i want to count the number of unique threads.Here thread is tid value. My Logfile looks like this-- Wed May 20 05:22:53.993 2009 Morocco Standard Time INFO: pid 2172 tid 688: 17: 10106931:... (9 Replies)
Discussion started by: namishtiwari
9 Replies
Login or Register to Ask a Question
PTHREAD_BARRIER(3)					   BSD Library Functions Manual 					PTHREAD_BARRIER(3)

NAME
pthread_barrier -- barrier interface LIBRARY
POSIX Threads Library (libpthread, -lpthread) SYNOPSIS
#include <pthread.h> int pthread_barrier_init(pthread_barrier_t * restrict barrier, const pthread_barrierattr_t * restrict attr, unsigned int count); int pthread_barrier_destroy(pthread_barrier_t *barrier); int pthread_barrier_wait(pthread_barrier_t *barrier); DESCRIPTION
The pthread_barrier_init() function creates a new barrier with attributes attr and count. The count parameter indicates the number of threads which will participate in the barrier. The pthread_barrierattr_init(3) function may be used to specify the attributes supplied in attr. If attr is NULL, the default attributes are used. Barriers are most commonly used in the decomposition of parallel loops. The pthread_barrier_destroy() function causes the resources allocated to barrier to be released. No threads should be blocked on barrier. The pthread_barrier_wait() function causes the current thread to wait on the barrier specified. Once as many threads as specified by the count parameter to the corresponding pthread_barrier_init() call have called pthread_barrier_wait(), all threads will wake up, return from their respective pthread_barrier_wait() calls and continue execution. RETURN VALUES
If successful, pthread_barrier_init() will return zero and put the new barrier id into barrier, otherwise an error number will be returned to indicate the error. If successful, pthread_barrier_destroy() will return zero. Otherwise an error value will be returned. If successful, pthread_barrier_wait() will return zero for all waiting threads except for one. One thread will receive status PTHREAD_BARRIER_SERIAL_THREAD, which is intended to indicate that this thread may be used to update shared data. It is the responsibility of this thread to insure the visibility and atomicity of any updates to shared data with respect to the other threads participating in the bar- rier. In the case of failure, an error value will be returned. ERRORS
The pthread_barrier_init() function may fail if: [EINVAL] The value specified by count is zero or attr is invalid. The pthread_barrier_destroy() function may fail if: [EBUSY] The barrier still has active threads associated with it. [EINVAL] The value specified by barrier is invalid. The pthread_barrier_wait() function may fail if: [EINVAL] The value specified by barrier is invalid. SEE ALSO
pthread_barrierattr(3), pthread_cond(3), pthread_mutex(3) STANDARDS
These functions conform to IEEE Std 1003.1-2001 (``POSIX.1''). BSD
July 8, 2010 BSD