On 01/04/2016 11:16 AM, Pranith Kumar Karampuri wrote:
Nice, I didn't know about this. What I am looking for with this tool
is even more granularity. i.e. per xlator information. It shouldn't be
so difficult to find information like time spent in each xlator. What
fop from fuse lead to what other fops in each of the xlator etc.
ltrace can be used to trace shared object calls made by any process. I
have used it for fuse clients too with appropriate filters that I'm
interested in. For eg: `ltrace -p <fuse_mount_pid> -e afr*` You can add
multiple filters too. :)
-Ravi
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
