search

BjoKaSH / maczfs-archive

Legacy MacZFS - Archived here due Google-code shutdown. Automatically exported from code.google.com/p/maczfs -- Do Not Use! Use https://openzfsonosx.org/
Other
1 stars 0 forks source link

Support DTrace for MacZFS #85

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
It would help with performance analysis if MacZFS supported DTrace. Since OSX 
doesn't support FBT for kernel loadable modules, we can't use that interface 
and will have to instrument additionally.

Original issue reported on code.google.com by alex.ble...@gmail.com on 27 Feb 2011 at 11:20

GoogleCodeExporter commented 9 years ago 
I've got the DTrace book on my near-term reading list, so I don't reckon this 
will languish any less if I say that I'll give it a go.

Original comment by buffer.g...@gmail.com on 4 Mar 2011 at 11:52

GoogleCodeExporter commented 9 years ago 
Just FYI I think there are a few places where the DTRACE_PROBE definitions are 
commented out, possibly in zfs_context.h. I'm also not sure how dtrace probing 
works in kernel land - maybe it would make sense to create a dummy kext as a 
standalone project to investigate how to do it. 

I put a bit on the wiki how the IOCTL and kernel stuff are related - you might 
be able to use that for testing traces. 

Also whilst ZFS isn't probeable directly, the VNOP_READ and others are. You 
might be able to set up a dtrace script to measure elapsed IO time using that.

Original comment by alex.ble...@gmail.com on 5 Mar 2011 at 12:14

GoogleCodeExporter commented 9 years ago 
MacZFS has been discontinued.  Please switch to https://openzfsonosx.org/

Original comment by googlelogin@bjoern-kahl.de on 28 Jul 2015 at 10:00