This callback(for registered clients) is used to notify the client whenever
**data is written** to the **ACTIVE replica**(Collocated or Non Collocated
checkpoints)
Following are the prototypes proposed to convert(or standardize!) these APIs to
SAF style (by incrementing the minor version to say, B.02.03):
1) SaCkptCallbacksT_2
typedef struct {
SaCkptCheckpointOpenCallbackT saCkptCheckpointOpenCallback;
SaCkptCheckpointSynchronizeCallbackT saCkptCheckpointSynchronizeCallback;
saCkptCheckpointTrackCallbackT saCkptCheckpointTrackCallback;
} SaCkptCallbacksT_2;
2) saCkptCheckpointTrackCallbackT
typedef void (*SaCkptCheckpointTrackCallbackT)(
SaCkptCheckpointHandleT checkpointHandle,
SaCkptIOVectorElementT *ioVector,
SaUint32T numberOfElements
);
3) saCkptInitialize_2()
Prototype
SaAisErrorT saCkptInitialize_2(
SaCkptHandleT *ckptHandle,
const SaCkptCallbacksT_2 *ckptCallbacks,
SaVersionT *version
);
Currently, this callback is registered/associated to a given client handle
SaCkptHandleT and therefore once registered, the callback will be invoked for
writes for any/all checkpoints associated with this client handle. The callback
carries information about the checkpoint to which the write has happened.
However, i'm exploring/estimating the feasibility to register this callback for
a given checkpoint i.e. SaCkptCheckpointHandleT, by for example providing a
track interface that registers the callback using the checkpointHandle rather
than the client handle, like as below:
4 . saCkptCheckpointTrack() .
This API will help the user to start receiving the track callback on a
checkpointHandle
Prototype
SaAisErrorT saCkptCheckpointTrack(
SaCkptCheckpointHandleT checkpointHandle
);
5 . saCkptCheckpointTrackStop() - To disable tracking for SaCkptHandleT
(client/application)
This API will help the user to stop receiving the track callback on a
checkpointHandle
Prototype
SaAisErrorT saCkptCheckpointTrackStop(
SaCkptCheckpointHandleT checkpointHandle
);
Will get back soon on the feasibility to support 4) and 5) without impacting
upgradeability.
---
** [tickets:#561] CKPT: add "CkptArrivalCallback" as part of the CKPT API**
**Status:** assigned
**Created:** Tue Sep 03, 2013 10:33 AM UTC by Hans Feldt
**Last Updated:** Tue Oct 01, 2013 03:43 PM UTC
**Owner:** A V Mahesh (AVM)
The OpenSAF implementation of CKPT adds a feature that closes a gap identified
and reported by SCOPE alliance in
http://scope-alliance.org/sites/default/files/documents/CG_MW_Profile_07_07_16_v2.0.pdf
The OpenSAF declaration of the extra function is not in the standard API
(saCkpt.h) but in cpsv_papi.h.
The purpose of this enhancement is to add this function to the standard API
with in "SAF style". This includes:
* adding a new callback type SaCkptCheckpointReplicaUpdateCallbackT
* adding a new callback in SaCkptCallbacksT_o2
* adding a new saCkptInitialize_o2 that takes SaCkptCallbacksT_o2 as a parameter
* calling the callback when the local (?) replica is updated
* clearly define the semantics of the function in the CKPT PR doc
* saCkptInitialize_o2 available with version B.02.11
please comment!
An alternative is to skip the _o2 and go for _2 and B.03.01
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
