Components for PAPI-C generally consist of a named folder containing source files and various other support files. For more details on creating a component of your own, see the documentation here and examples of other components distributed with PAPI here.
If you want to view information about other available components, click one of the component names at the bottom of this page.
You must be logged into a pre-approved account to add or edit component information.
To contribute a component that you've written, enter a descriptive name for your component in the box below, and press the button. This will become the name of the page that describes your component. If that page already exists, you will be directed to a form to edit that page.
For an illustration of what your Component page will look like, visit the Component Example page or other Component pages.
Please refresh the page to see the changes
|Last modified||Component overview|
|CUDA||2455903.58 December 2011||Provides access to hardware counters inside NVIDIA GPUs through the CUDA / CUPTI interface|
|Component Example||2455707.526 May 2011||This is a short description of what your component does.|
|CoreTemp||2455872.57 November 2011||Access hardware sensors through the coretemp sysf interface|
|Coretemp freebsd||2455872.57 November 2011||Access hardware temperature sensors on FreeBSD|
|Example||2455954.528 January 2012||Example component code with 3 counters|
|Infiniband||2455872.57 November 2011||Infiniband Network Component|
|Lm-sensors||2455958.51 February 2012||Component interface for lm-sensors system health measurement|
|Lustre||2455956.530 January 2012||Measure performance data on a Lustre filesystem|
|Vmware||2455956.530 January 2012||Provides access to counters provided by VMware's Guest SDK as well as optional virtual timing counters.|
Instead of constantly bugging Kiran with emails, I'm keeping Notes.