search

darshan-hpc / darshan

Darshan I/O characterization tool
Other
56 stars 27 forks source link

dxt module does not log metadata operations #318

Open shanedsnyder opened 3 years ago

shanedsnyder commented 3 years ago

In GitLab by @glennklockwood on Apr 25, 2021, 18:19

I'm trying to trace several different metadata-heavy applications and have been resorting to bolting on a lot of new functionality to librecorder, but I am tripping over the same gotchas that Darshan already solved (like __open_2) and would rather invest time into extending Darshan.

Was metadata tracing left out of DXT purposely? If not, I'd like to explore the cleanest way to add DXT logging of more than just reads and writes.

shanedsnyder commented 3 years ago

In GitLab by @shanedsnyder on Apr 28, 2021, 09:10

I don't think it was left out for any particular reason, just that the original developers focused their attention solely on read/write activity. Seems completely reasonable to update it to trace more than that, though.

I imagine it's relatively straightforward to abstract the current instrumentation so that it doesn't just record read/write "segments", but captures some fixed parameters for different types of calls (I/O and metadata). Probably just prefix each record with an operation type identifier, then use a union data structure for holding the relevant params for each operation type?