Merge Darshan eXtended Tracing (DXT) to Darshan Main stream

See merge request !2

Get Fortran executable arguments

We usually work with Fortran programs and it is always useful to have the arguments of the executable in the Darshan log. This feature allows Drshan to get the executable name and the arguments from /proc/self/cmdline if the program is Fortran (argc==0)

See merge request !3

Signed-off-by: Cong Xu <congxu@localhost.localdomain>

no instrumenation_disabled flags are needed since this
functionality will be managed by the overlying MPI-IO and POSIX
modules (DXT calls are embedded in wrappers in these modules).

Signed-off-by: Cong Xu <congxu@localhost.localdomain>

Signed-off-by: Cong Xu <cong.xu@intel.com>

Signed-off-by: Cong Xu <cong.xu@intel.com>

Signed-off-by: Cong Xu <cong.xu@intel.com>

Signed-off-by: Cong Xu <cong.xu@intel.com>

Signed-off-by: Cong Xu <cong.xu@intel.com>

1. At log parsing time, pass Lustre striping information to DXLT module
  a. Obtain Lustre striping information in Lustre Module.
  b. Cache file striping information and map it to file name.
  c. Pass file striping information to DXLT module for each file.

2. In DXLT module, print Lustre striping and OST information if file system type is Lustre.

Signed-off-by: Cong Xu <cong.xu@intel.com>

2. Refactor DXLT to be a generic IO tracing tool for files on any file system.
3. Add file type information in DXLT log parser.

Next steps:
1. Based on the file type information in DXLT log parser, add information for specific file types. (For instance, add OST information for files on Lustre)
2. In the process of parsing DXLT logs, figure out how to obtain Lustre striping information from Lustre module.
3. Rename DXLT to be "Darshan eXtended Tracing (DXT)" or "Darshan eXtended IO Tracing (DXIOT)".

Signed-off-by: Cong Xu <cong.xu@intel.com>