Hi, I have been able to successfully monitor synchronous I/O events to a larger degree, but I can''t with asynchronous I/Os. For example, when a synchronous I/O is issued, it can be tracked through io:::start as well as io:::done. With an asynchronous I/O, it is possible to track when it''s initiated(io:::start), but not when it''s done(io:::done). Is my understanding correct? If so, it is probably be due to the way it''s implemented/returned, but would like to hear it from DTrace experts. many thanks. Senthil
senthil ramanujam writes: > Hi, > > I have been able to successfully monitor synchronous I/O events to a > larger degree, but I can''t with asynchronous I/Os. For example, when a > synchronous I/O is issued, it can be tracked through io:::start as > well as io:::done. With an asynchronous I/O, it is possible to track > when it''s initiated(io:::start), but not when it''s done(io:::done). Is > my understanding correct? If so, it is probably be due to the way it''s > implemented/returned, but would like to hear it from DTrace experts. > > many thanks. > Seems like this is a misinterpretation. Tell us a lot more about what you''re seeing. -r > Senthil > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org