I have two threads with WRITE/READ between them. The synchronisation works (I use pthread library) but I must calculate the execution of the READ function.
A part of my program :
Actually, GET_TIME uses gethrtime() => it's system time. But between my two GET_TIME, I'm not sure that only this function is executed. Processor switchs between thread 1 and 2 so waitdur is variable, that's why I want to know a solution to calculate only thread time.
How to post a new thread (Regarding Unix related doubts) in Unix Forums.
I registered my id but I am unable to post my Questions to Forum.
Thanks & Regards,
indusri (1 Reply)
Hello
Ive written 2 programs in shell and I need to compare their speed (Compile) against one another.
what methods could I go about doing this?
Is there a feature in shell do accommodate this? (2 Replies)
I am working on an application with some rather interesting build performance issues. If we build on Solaris/Linux x86/AMD64 the build is rather fast, but it takes more than five times as long on our Solaris Sparc servers (single-threaded builds on the workstations, but multi-threaded on the... (5 Replies)
hi there, i'd like to know what exactly zpool's iostat (-v) output measure, especially the writes. Is it only the writes to the ZIL or all writes (including commmits) to the disks? if anyone knows, that'd be helpful roti (1 Reply)
Hi
For our load testing , we are using stubs (unix shell script) which send the response to the request coming from the application. As the unix stub is single threaded , it is responding to only one request whereas multiple requests come in parallely.
I haven't worked on thread concepts... (5 Replies)
Hello guys,
I am doing a performance analysis on one of our psystem. Most of time I am using Nmon analyser to do my trend graph. But I can't find any help with it. We are interesting in the time spend by tasks in Aix run queue.
After looking the Aix documentation, I am pessimist to find any... (3 Replies)
Hi
I have a system running solaris 10, and I intend to use a NetApp as its storage system. The application requires a throughput between the server and the storage 7000 disk IOPS (random IO sustained throughput with response time of 20 mili second and 16k block size).
How to make sure that I... (6 Replies)
Greetings!
I set up a basic threading specimen which does the job:#!/usr/bin/python
import threading
class a(threading.Thread):
def __init__(self):
threading.Thread.__init__(self)
def run(self):
print("thread a finished")
class b(threading.Thread):
... (0 Replies)
Discussion started by: LinQ
0 Replies
LEARN ABOUT SUNOS
pthread_barrier_wait
pthread_barrier_wait(3C) Standard C Library Functions pthread_barrier_wait(3C)NAME
pthread_barrier_wait - synchronize at a barrier
SYNOPSIS
cc -mt [ flag... ] file... [ library... ]
#include <pthread.h>
int pthread_barrier_wait(pthread_barrier_t *barrier);
DESCRIPTION
The pthread_barrier_wait() function synchronizes participating threads at the barrier referenced by barrier. The calling thread blocks
until the required number of threads have called pthread_barrier_wait() specifying the barrier.
When the required number of threads have called pthread_barrier_wait() specifying the barrier, the constant PTHREAD_BARRIER_SERIAL_THREAD
is returned to one unspecified thread and 0 is returned to each of the remaining threads. At this point, the barrier is reset to the state
it had as a result of the most recent pthread_barrier_init(3C) function that referenced it.
The constant PTHREAD_BARRIER_SERIAL_THREAD is defined in <pthread.h> and its value is distinct from any other value returned by
pthread_barrier_wait().
The results are undefined if this function is called with an uninitialized barrier.
If a signal is delivered to a thread blocked on a barrier, upon return from the signal handler the thread resumes waiting at the barrier if
the barrier wait has not completed (that is, if the required number of threads have not arrived at the barrier during the execution of the
signal handler); otherwise, the thread continues as normal from the completed barrier wait. Until the thread in the signal handler returns
from it, it is unspecified whether other threads may proceed past the barrier once they have all reached it.
A thread that has blocked on a barrier does not prevent any unblocked thread that is eligible to use the same processing resources from
eventually making forward progress in its execution.
Eligibility for processing resources is determined by the scheduling policy.
RETURN VALUES
Upon successful completion, the pthread_barrier_wait() function returns PTHREAD_BARRIER_SERIAL_THREAD for a single (arbitrary) thread syn-
chronized at the barrier and 0 for each of the other threads. Otherwise, an error number is returned to indicate the error.
ERRORS
The pthread_barrier_wait() function will fail if:
EINVAL The value specified by barrier does not refer to an initialized barrier object.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO pthread_barrier_destroy(3C), attributes(5), standards(5)SunOS 5.10 30 Jan 2004 pthread_barrier_wait(3C)