Displaying 3 results from an estimated 3 matches for "cv_block".
Did you mean:
v_block
2008 Feb 12
1
measuring sleep time in synchronization objects
...m(walltimestamp - bedtime[args[0]->pr_addr,args[0]->pr_stype]);
bedtime[args[0]->pr_addr,args[0]->pr_stype] = 0;
}
On running my program along with this script, I could see (because of
ustack()) that the program is following the expected path to sem_wait() call
and then enters cv_block:sleep. The aggregation output showed that the
threads in my program are sleeping on pr_stype = 3 (translates to SOBJ_CV
according to the file sobject.h). However, I was expecting to see the
threads sleeping on pr_stype = 5 (SOBJ_USER) as a result of sem_wait()
calls, because the description of pr_s...
2006 Mar 30
8
iostat -xn 5 _donot_ update: how to use DTrace
on Solaris 10
5.10 Generic_118822-23 sun4v sparc SUNW,Sun-Fire-T200
I run
#iostat -xn 5
to monitor the IO statistics on SF T2000 server. The system also have a heavy IO load, for some reason iostat donot refresh (no any update). It seems like iostat is calling pause() and stucked there. Also my HBA driver''s interrupt stack trace indicates there is a lot of swtch(), the overall IOPS
2011 Aug 19
4
Using dtrace to follow a kernel linked list
I''m looking for an example of how one could write a dtrace probe
that could follow something like a NULL terminated linked list.
For example:
struct list {
struct list *next;
void *data;
};
struct list *list_root;
Assuming I had "list_root" available, but I wanted to know how long
the linked list is, how can I do this in a dtrace probe?
If I had looping