1. 10 Jun, 2016 1 commit
  2. 09 Jun, 2016 1 commit
  3. 08 Jun, 2016 2 commits
  4. 06 Jun, 2016 1 commit
    • Shane Snyder's avatar
      add record_ref interface to darshan-common · 9bfc7b65
      Shane Snyder authored
      This interface provides some convenience functions for mapping
      opaque record identifiers (could be a filename, file descriptor,
      or any other type of file handle) to a corresponding runtime
      structure referencing the actual file record. This runtime
      structure should at least contain a pointer to the actual file
      record, and can also persist arbitrary state for this record.
      9bfc7b65
  5. 31 May, 2016 1 commit
    • Shane Snyder's avatar
      numerous darshan-core api changes · bfde9eb7
      Shane Snyder authored
      - memory management is now entirely handled by darshan-core for
        module records
          * when registering new records, darshan-core returns the
            corresponding buffer to write it to, rather than allowing
            module to determine this
      - modules now decide whether darshan-core should track record
        names by passing either a valid name or NULL to the register
        function
          * this allows modules to register records that aren't really
            tracked by darshan-core
      - only the POSIX module has been ported to new changes for this
        commit
      bfde9eb7
  6. 27 May, 2016 1 commit
  7. 29 Jan, 2016 1 commit
  8. 20 Jan, 2016 1 commit
  9. 18 Jan, 2016 1 commit
    • Shane Snyder's avatar
      update how module & record registration · d3fae782
      Shane Snyder authored
      - modules now receive a memory buffer after successfully
      registering with darshan-core. modules can request a specific
      memory amount, but may not be honored depending on the configured
      darshan memory limit
      - split the previous register_record function into 2 parts:
          * lookup() -> lookup darshan_record_id corresp. to path name
          * register() -> register record_id & name with darshan-core
      - register_record now returns true if the record added; false
      otherwise (if module was out of memory or darshan is out of memory
      for storing id->name mappings)
      d3fae782
  10. 11 Dec, 2015 1 commit
  11. 04 Dec, 2015 1 commit
  12. 01 Dec, 2015 1 commit
  13. 02 Nov, 2015 1 commit
  14. 12 Oct, 2015 1 commit
  15. 06 Aug, 2015 1 commit
  16. 22 Jul, 2015 1 commit
  17. 20 Jul, 2015 1 commit
  18. 14 Jul, 2015 1 commit
  19. 15 Apr, 2015 1 commit
  20. 08 Apr, 2015 1 commit
  21. 06 Apr, 2015 1 commit
  22. 03 Apr, 2015 1 commit
  23. 02 Apr, 2015 1 commit
  24. 01 Apr, 2015 1 commit
  25. 30 Mar, 2015 2 commits
  26. 26 Mar, 2015 1 commit
  27. 25 Mar, 2015 2 commits
  28. 12 Mar, 2015 1 commit
  29. 06 Mar, 2015 1 commit
  30. 05 Mar, 2015 1 commit
  31. 02 Mar, 2015 1 commit
  32. 19 Feb, 2015 1 commit
  33. 11 Feb, 2015 1 commit
  34. 10 Feb, 2015 1 commit
  35. 22 Jan, 2015 1 commit
  36. 16 Jan, 2015 1 commit
  37. 20 Nov, 2014 1 commit
    • Shane Snyder's avatar
      Complete (first) implementation for darshan · da477e42
      Shane Snyder authored
      -darshan-core:
          - initializes darshan job data structures
          - creates log file
          - writes job info header
          - reduces which modules were used locally/globally
          - shut down and write out individual modules one by one
      
      -darshan-posix:
          - register w/ darshan-core and allocate allowed memory
          - track open counter and timestamp for opened files
          - provide file record buffer at shutdown
      
      Major TODOs:
          - shared file reductions (prefer reusable across modules)
          - register handles with darshan file_ids (prefer reusable)
          - generic compression of module buffers (zlib/bzip2)
          - write out map of filenames to darshan ids
          - modify darshan-util and add darshan-posix parser to read logs
      da477e42