-------- Original Message -------- Subject: patches: karma Date: Thu, 18 May 2006 17:10:34 +0200 From: Phil Carns <[EMAIL PROTECTED]> To: PVFS2-developers <[email protected]>
perf-mon.patch: ---------------- This fixes two bugs in the performance monitoring path. This isn't specific to karma, but karma is the tool most affected. There was a bug in how the timestamps were filled into the response structure, which probably showed up mainly when multiple timesteps are requested. In addition, the metdata counts were supposed to be cumulative, but they had been set to restart at zero on each interval. karma1.patch: -------------- This fixes a karma bug in how it tracks metadata counts. It wasn't properly tracking the previous values from each iteration to compute the difference (since the values are cumulative). karma2.patch: -------------- This is a trivial patch to make sure karma complains if you pass it command line arguments (since none are supported). This is mainly to make sure no one does a "-m /mnt/pvfs2-foo" to specify a particular file system, which may appear to work at first. karma3.patch: -------------- This is a code reformatting patch. Sorry its in the middle of the series rather than the end (found some other items later). It not only adjusts the code format, but also adds proper copyright headers and editor directives. karma4.patch: -------------- This is a somewhat odd patch, but it adds a new configure script argument called "--disable-karma-mem-usage-stats". This option will cause karma to _not_ display the column that shows memory usage on each server. The reason for this is that (depending on who you deploy this program for) this statistic can be confusing. It doesn't differentiate between memory truly in use, and available memory that is temporarily in use by the buffer cache. At first glance the servers just look like they are almost out of memory at all times. I originally wanted to just make the display show available memory taking buffer cache into account, but I couldn't find any clean way to do it (would require /proc file parsing). So this just cuts the display out for people who might be concerned about this. karma5.patch: --------------- This fixes a variety of error handling cases in karma (if a server is not responding, or does not match protocol version, for example): - clean up error messages (displayed in bottom pane) - include host names when possible - handle error codes that don't generage EDETAIL type output - stop statistics gathering on certain types of errors (and display a message warning that restarting karma will be necessary to resume). -Phil
karma1.patch.gz
Description: application/gzip
karma2.patch.gz
Description: application/gzip
karma3.patch.gz
Description: application/gzip
karma4.patch.gz
Description: application/gzip
karma5.patch.gz
Description: application/gzip
perf-mon.patch.gz
Description: application/gzip
_______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
