[dtrace-discuss] Multiple returns from a syscall
Jesus Cea
jcea at argo.es
Tue Jun 5 12:27:38 PDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Adam Leventhal wrote:
> Note that DTrace output is presented one CPU at a time rather than sorted
> chronologically. Without seeing the full output from DTrace, one wouldn't
> be able to draw any conclusions about a 'missing' entry. I suggest you
> trace the timestamp in addition and then sort based on that column or
> pbind the process to a specific CPU when doing this sort of analysis.
Oh, I see. That could explain it. How can I sort the data by timestamp?.
Must I "printf" the timestamp and postprocess the data manually?
"pbind" seems to work fine.
Now, I must investigate why some "fdsync" are so painfully slow. Some
take >5 seconds...
- --
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea at argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/
jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/_/_/_/
_/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBRmW5Kplgi5GaxT1NAQLMLQQAg+KxhVaJEuMIhS3qVai+sQHA/psiLX98
KyRspd6+esyBmAU149Vg9BEBTtmwRz7lW/jpyoahE3GH7xsKUvahSIvBlKEdzYHm
QyEuWEGrsdcFb6U15JHLpzLsiM0V63uDJsud7t/nWGdO7PT5ahi1cFj8lYMFvhed
J4ONNdNFzhk=
=fapT
-----END PGP SIGNATURE-----
More information about the dtrace-discuss
mailing list