Motorola 6806800C47B manual Service Dependencies, Shared Memory Configuration

Page 21

Shared Memory Configuration

API Description

 

 

2.3.1Shared Memory Configuration

NCS3.0 Checkpoint service uses the shared memory for storing the checkpoint replicas. Checkpoint service will manage the shared memory segments created by it for storing the checkpoint replicas. The shared memory requirements for storing the checkpoint replica can be derived from the checkpoint creation attributes supplied at the time of saCkptCheckpointOpen( ) or saCkptCheckpointOpenAsync( ) call using the formula. maxSections * maxSectionSize

The maximum size of the shared memory segment is limited by the operating system. In most of the cases, the maximum value is 31MB. This can be found by executing the command: cat /proc/sys/kernel/shmmax

To increase the shared memory size to the desired value, one can use the following command: echo 134217728 >/proc/sys/kernel/shmmax

The above example command will set the maximum shared memory segment value to 27MB.

2.3.2Maximum Data Size Per One write or Overwrite

The maximum data size per one write or over write is 40MB. Applications that try to write more than 40MB data in one saCkptSectionWrite( ) or saCkptSectionOverwrite( ) call will get the error SA_AIS_ERR_NO_RESOURCES.

2.4Service Dependencies

The internal interfaces of the Checkpoint service are given below:

zLayered Environment for Accelerated Portability (LEAP) - for Shared Memory: Checkpoint Service uses LEAP for portability. The service uses the memory manager, timers, encode- decode utility and handle manager services provided by the LEAP.

zMessage Distribution Service (MDS) - for Messaging: All the interaction between the different subparts of the Checkpoint service will take place using MDS messaging. The MDS is also used to register the service up and down events to handle the failure cases.

zDistributed Tracing Service (DTSv) - for Logging messages: Checkpoint service uses DTSv to log debug messages, which are stored in a file and could be used for debugging and to report informational events.

zAvailability Service (AvSv) - for High Availability: CPD and CPND are modelled as AMF components.

zMessage based Checkpoint Service (MBCSv) - for checkpointing information: CPD uses the MBCSv to checkpoint the state information with the standby CPD.

zCluster Membership Service (CLM) - for Node names: CPD uses Cluster membership service to get the node name for a given node ID. Node names are required to implement Checkpoint service MIBs.

The Checkpoint library libSaCkpt.so depends on functions found in the following library: libncs_core.so

Checkpoint Service Programmer’s Reference (6806800C47B)

21

Page 20 Page 22
Image 21
Page 20 Page 22
Contents Checkpoint Service Trademarks Contents Contents List of Tables List of Tables List of Figures Checkpoint Service -SubpartsList of Figures Overview of Contents About this ManualAbbreviations About this Manual Abbreviation Definition ConventionsNotation Description BoldComments and Suggestions Summary of ChangesAbout this Manual Part Number Publication Date DescriptionAbout this Manual Overview IntroductionCheckpoint Director Models and ConceptsCheckpoint Node Director Introduction Models and ConceptsCompliance Report Compliance Table Checkpoint ServiceCheckpoint Agent Checkpoint Agent IntroductionIntroduction Related SAF Standard Documents Related SAF Standard DocumentsAPI Description Service ExtensionsNcsCkptRegisterCkptArrivalCallback NcsCkptRegisterCkptArrivalCallback ParametersNcsCkptRegisterCkptArrivalCallback Return Values 2 *ncsCkptCkptArrivalCallbackNcsCkptCkptArrivalCallback Parameters API Description NcsCkptCkptArrivalCallbackImplementation Notes Usage of Non-Collocated CheckpointsImplementation Notes API Description Time-out Arguments for Checkpoint Service APIs ConfigurationCancellation of Pending Callbacks Maximum Number of Replicas Per NodeShared Memory Configuration Service DependenciesShared Memory Configuration API Description Maximum Data Size Per One write or OverwriteManagement Interface SAF-CHK-SVC-v75 MIBMIB table id \ trap id Description Sample Application Run the Checkpoint Service DemoSample Application Sample Application Output Sample Application OutputMotorola Embedded Communications Computing Documents Related DocumentationTable B-1 Motorola Publications Document Title Publication NumberTable B-2 Related Specifications 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