[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-dtrace-discuss
Subject:    Re: [dtrace-discuss] track program time - need some guidelines
From:       Jim Mauro <James.Mauro () Sun ! COM>
Date:       2009-07-13 13:20:34
Message-ID: 4A5B34A2.70309 () sun ! com
[Download RAW message or body]

Threads are put to sleep when they issue blocking system calls.
I'm not sure exactly what you mean by "only know synchronous
app wait from an app perspective....", but the threads will be in the
sleep state (SLP) after issuing the read/write until the data is
available, at which point a wakeup is issued and the thread goes to
runnable.

You're conspicuously avoiding answering the "what problem are you
trying to solve question", which has been asked multiple times.

This is no longer a DTrace question, so any further queries should get
posted to the performance forum.

/jim


tester wrote:
> Thanks everyone. A quick question, where would be the time be accounted for a \
> thread that wait for a write/read syscall to a block device? I would only like to \
> know the synchronous app wait from an app  perspective irrespective of all the \
> async activities that supports it. I havn't looked at Sun studio yet since I don't \
> think I can install it our env. Time for me go and re-read the thread again,I \
> guess. 
> Thanks again.
> 
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org


[prev in list] [next in list] [prev in thread] [next in thread]