Collaboration diagram for Throughput Performance Plugin:
![]() |
Note: Since this plugin is built on top of the Performance Marker Plugin, it is not possible to associate both plugins with a handle
|
Module descriptor.
|
|
Transfer begin callback This callback will be called when a transfer begins.
|
|
Stripe performace throughput callback This callback will be called with every performance callback that is received by the perf plugin. The first callback for each stripe_ndx will have an instantaneous_throughput based from the time the command was sent.
|
|
Total performace throughput callback This callback will be called with every performance callback that is received by the perf plugin. The first callback for will have an instantaneous_throughput based from the time the command was sent. This callback will be called after the per_stripe_cb
|
|
Transfer complete callback This callback will be called upon transfer completion (successful or otherwise).
|
|
Copy constructor This callback will be called when a copy of this plugin is made, it is intended to allow initialization of a new user_specific data.
|
|
Destructor This callback will be called when a copy of this plugin is destroyed, it is intended to allow the user to free up any memory associated with the user specific data.
|
|
Throughput plugin init Use this function to initialize a throughput plugin. The throughput plugin sits on top of the perf_plugin. The only required param is 'plugin', all others may be GLOBUS_NULL
|
|
Set user copy and destroy callbacks Use this to have the plugin make callbacks any time a copy of this plugin is being made. This will allow the user to keep state for different handles.
|
|
Destroy throughput plugin Frees up memory associated with plugin.
|
|
Retrieve user specific pointer.
|
about globus |
globus toolkit |
dev.globus
Comments? webmaster@globus.org