Motorola 6806800C47B manual Configuration, Time-out Arguments for Checkpoint Service APIs

Page 20

API Description

Time-out Arguments for Checkpoint Service APIs

 

 

Creating extra replicas on the system manager node for non-collated checkpoints is an overhead. The advantage of a non-collocated checkpoint is that replica will be created in two places, no matter from how many nodes it is opened.

2.2.2Time-out Arguments for Checkpoint Service APIs

For all synchronous API calls, the application will provide the “timeout” argument. The application will consider invocation of the particular API failed in case it did not complete the call by the specified time. CPSv requires that the value passed in the timeout argument is greater than 100000000 nano seconds (100 milliseconds).

2.2.3Cancellation of Pending Callbacks

According to the SAF-AIS-CKPT-B.01.01 specification, whenever a checkpoint is closed, all the pending callbacks corresponding to this checkpoint should be cancelled. In CPSv, implementation does cancel the pending callbacks related to closed checkpoints. However, the selection object already raised and related to cancelled pending callbacks, will not be cleared or reset. Due to this, saCkptDispatch API may return without invoking callback routine.

2.2.4Maximum Number of Replicas Per Node

CPSv applications can create upto 1,000 replicas per node at a given instance. This includes the replicas created by CPSv for non-collocated checkpoints as per the “replica creation policy.”

In the case of collocated checkpoints, CPSv returns SA_AIS_ERR_NO_RESOURCES if an application attempts to create a new checkpoint and the current number of replicas on the local node is already the maximum that CPSv can support per node.

In the case of non-collocated checkpoints, CPSv returns an SA_AIS_ERR_NO_RESOURCES if the number of checkpoint replicas on the node on which CPSv decides to create a replica is already the maximum that CPSv can support per node. In all other cases, the checkpoint open does not return an error but the replicas will not be created on the backup nodes as decided by the “replica creation policy”.

2.2.5Handling of SA_AIS_ERR_TRY_AGAIN

If the Checkpoint service API returns SA_AIS_ERR_TRY_AGAIN, the application should attempt the API call only after a couple of milliseconds. The suggested wait time is 3 seconds and the number of retries are 12.

Note that the Checkpoint write,overwrite, and read operations may sometime return

SA_AIS_ERR_TRY_AGAIN if called simultaneously. This is to avoid any inconsistencies in the checkpoint database.

2.3Configuration

This section describes how the Checkpoint service is preconfigured regarding shared memory and the maximum write data size.

20

Checkpoint Service Programmer’s Reference (6806800C47B)

Page 19 Page 21
Image 20
Page 19 Page 21
Contents Checkpoint Service Trademarks Contents Contents List of Tables List of Tables Checkpoint Service -Subparts List of FiguresList of Figures Abbreviations Overview of ContentsAbout this Manual Conventions About this Manual Abbreviation DefinitionNotation Description BoldSummary of Changes Comments and SuggestionsAbout this Manual Part Number Publication Date DescriptionAbout this Manual Introduction OverviewModels and Concepts Checkpoint DirectorCheckpoint Node Director Introduction Models and ConceptsCompliance Table Checkpoint Service Compliance ReportCheckpoint Agent Checkpoint Agent IntroductionRelated SAF Standard Documents Introduction Related SAF Standard DocumentsService Extensions API DescriptionNcsCkptRegisterCkptArrivalCallback NcsCkptRegisterCkptArrivalCallback Parameters2 *ncsCkptCkptArrivalCallback NcsCkptRegisterCkptArrivalCallback Return ValuesNcsCkptCkptArrivalCallback Parameters API Description NcsCkptCkptArrivalCallbackImplementation Notes API Description Implementation NotesUsage of Non-Collocated Checkpoints Configuration Time-out Arguments for Checkpoint Service APIsCancellation of Pending Callbacks Maximum Number of Replicas Per NodeService Dependencies Shared Memory ConfigurationShared Memory Configuration API Description Maximum Data Size Per One write or OverwriteMIB table id \ trap id Description Management InterfaceSAF-CHK-SVC-v75 MIB Run the Checkpoint Service Demo Sample ApplicationSample Application Output Sample Application Sample Application OutputRelated Documentation Motorola Embedded Communications Computing DocumentsTable B-1 Motorola Publications Document Title Publication NumberRelated Specifications Table B-2 Related SpecificationsRelated Documentation Related Specifications Document Title Version/Source

6806800C47B specifications

The Motorola 68000 series microprocessor, which includes the 68000, 68010, 68020, and others, significantly impacted the development of computing technology. Among its variants is the Motorola 68000, often referenced for its advanced features, performance, and capacity for versatility, making it one of the most prominent processors in its time.

The Motorola 68000, with its 16-bit data bus and 32-bit internal architecture, provided a potent combination of speed and efficiency. This processor features a clock speed ranging from 5 to 25 MHz, enabling high-performance computing for a range of applications, from personal computers to embedded systems. It utilizes a sophisticated instruction set that accommodates complex operations, enabling developers to write efficient and powerful software.

One of the main characteristics of the Motorola 68000 is its ability to address 24 bits of memory space, allowing it to access up to 16 MB of RAM directly. This memory addressing capability was an impressive feature during its release, supporting more extensive and more complex applications than most contemporaries could handle at the time.

The architecture of the Motorola 68000 is notable for its orthogonal design, which provides a rich set of addressing modes, making it versatile for various programming tasks. Its instruction set includes operations for arithmetic, logic, and data manipulation, coupled with strong support for multitasking and complex data structures, essential for modern operating systems.

In terms of technology, the Motorola 68000 employed a dual-processor architecture that enabled it to work alongside other processors, such as the Motorola 68881 and 68882 floating-point coprocessors, significantly enhancing its computational capabilities especially in graphics, scientific calculations, and complex algorithms.

Furthermore, the 68000 series processors were known for their excellent interrupt handling capabilities, making them suitable for real-time applications. This feature was particularly valuable in embedded systems, telecommunications, and industrial control systems, allowing for responsiveness in processing external events.

The 68000 microprocessor also gained popularity in the world of gaming and graphics, being utilized in iconic devices like the Sega Genesis and the Atari ST series. Its performance and flexibility in diverse applications ensured that the 68000 series left an indelible mark on the evolution of computing technology, influencing generations of system design.

In conclusion, the Motorola 68000, particularly the 68000 series, is a foundation in microprocessor history, celebrated for its capabilities in memory management, software development, and multi-faceted applications that paved the way for modern computing.
Top Page Image Contents