Skip to content
Mario Bielert edited this page Jun 29, 2017 · 9 revisions

The async policy is used to create asynchronous metrics. As the name suggests, such metrics are running asynchronous to the actual instrumented application, e.g., energy measurements on external devices.

This policy is mutually exclusive with the sync policy and the sync_strict policy.

This policy conflicts with the synchronize policy.

This policy requires the scorep_clock policy.

Required methods

void start()

This method gets called, when the measurement should be started.

void stop()

This method gets called, when the measurement should be stopped.

template <class Cursor> void get_all_values(std::int32_t id, Cursor& c)

This function gets called, after the measurement was stopped, or after delta_t ticks.

Arguments:

  • id - the id returned to Score-p in add_counter() (See Base)
  • c - the Cursor used to write data

Optional methods

void synchronize(bool is_responsible, SCOREP_MetricSynchronizationMode mode)

This method gets called to synchronise the time between the plugin, Score-P and the measurement.

Arguments:

  • is_responsible - signalises, whether the thread is used responsible to do the time synchronisation, e.g. master thread
  • mode - gives a hint, the the synchronisation is called

Provided methods

This policy doesn't provide any methods.

See also

Clone this wiki locally