JPH02108148A - Portable shared memory control system - Google Patents

Abstract

PURPOSE:To utilize the same control system by making a computer system, shared memory pool, or task different and a memory control table and a task interface equal. CONSTITUTION:The memory control table 2 depends upon neither the computer system nor shared memory pool and contains the assignment state of the shared memory and assignment memory size. Further, a memory control means 1 has the task interface which depends upon neither the computer system nor task and operates the memory control table 2 at a request from the task to control the assignment state of the memory in the shared memory table, thereby inspecting the propriety of the reading, writing, and releasing of data on the memory. Consequently, the same control system can be utilized and high- reliability memory control is performed.

Description

DETAILED DESCRIPTION OF THE INVENTION (Field of Industrial Application) The present invention relates to a portable shared memory management method, particularly for computers in which multiple tasks that use memory on a shared memory pool exclusively and temporarily run simultaneously. This invention relates to a portable shared memory management method in a system.

(Conventional technique ftj) Conventional shared memory management methods have memory management tables that depend on the computer system and the shared memory pool,
Or 3 in total! It had a task-to-task interface that depended on the machine system and task.

(Problem to be Solved by the Invention) In the conventional shared memory management method, different computer systems, shared memory pools, or tasks have different memory management tables or task interfaces, and incompatible There was a problem in that each shared memory management method had to be maintained and maintained independently.

(Means for Solving the Problem) The portable shared memory management method according to the present invention is a portable shared memory management method for a computer system in which a plurality of tasks that use memory on a shared memory pool exclusively and temporarily operate simultaneously. The management method includes a memory management table that does not depend on a computer system and a shared memory pool and stores the allocation state and allocated memory size of the shared memory, and a task-to-task interface that does not depend on the computer system and the task; The memory management means operates the memory management table according to a request from the shared memory pool, manages the allocation state of memory on the shared memory pool, and checks the validity of reading, writing, and releasing data to the memory.

(Example) The present invention will be explained based on the drawings.

Referring to FIG. 1, one practical example of the present invention is comprised of a memory management means 1 and a memory management table 2.

FIG. 2 shows an example of the memory management table 1, which is composed of an entry number cell 21 and a memory state table 22. Each entry in the memory status table 22 has a memory ID item 221 and a task ID item 2.
22 and a memory size item 223. The value n is the ``memory allocation'' two-limit value. The memory state table 22 is always used continuously starting from the first entry, and the number of the last entry in use is represented by the entry number cell 21. The initial state of the memory state table 22 is such that no entries are used, and the initial value of the entry number cell 21 is 0.

FIG. 3 shows a memory allocation registration interface,
Examples of task-to-task interfaces are shown for memory release checking interfaces and memory access checking interfaces. Next, the memory allocation registration, memory release check, and memory access check will be explained in detail with reference to FIGS. 4, 5, and 6.

FIG. 4 is a flowchart illustrating the processing flow of the memory management means I when a task specifies a memory ID and memory size and requests memory allocation registration.

The memory management means 1 acquires the task ID of the requesting task (Step 41), and stores it in each item along with the memory ID and memory size specified in the entry immediately after the last entry in the memory status table 22 (Step 4).
2) After that, the value of the entry number cell 21 is increased by 1 (step 43), and the process ends.

FIG. 5 is a flowchart illustrating the processing of the memory management means 1 when the memory 1d is designated by a task and a memory release check is requested.

The memory management means 1 searches the memory status table 22 for the first entry with the same memory ID as the specified memory ID (step 51), and confirms that the task ID of that entry is the same as the task ID of the requesting task. (Steps 52.53).

After that, the value of each item of each entry from immediately after that entry to the last entry is sequentially moved one entry earlier (step 54), and the value of the number of entries cell 21 is subtracted by 1 (step 55), so that it is normal. finish. If there is an entry with the same memory ID as the specified memory ID, or even if there is, the task ID of the entry and the task ID of the requesting task are not the same, the process terminates abnormally when it is detected.

FIG. 6 is a flowchart illustrating the processing of the memory management means 1 when a task specifies a memory ID, an access address (to solve a problem, and an access size) and requests a memory access check.

The memory management means 1 searches the memory status table 22 for the first entry with the same memory ID as the specified memory ID (step 61), and confirms that the task ID of that entry is the same as the task ID of the requesting task. Steps 62 and 63>. Confirm that the access start address and access size do not exceed the memory size of the sono entry (step 64 and 65). If confirmed, the process ends normally. If there is no entry with the same memory ID as the specified memory ID, or even if there is, the task 1d of the entry and the task ID of the requesting task are not the same, or the access start address and access size exceed the memory size of the entry. will terminate abnormally.

(Effects of the Invention) As described above, the portable shared memory management method of the present invention allows the same management method to be used even if the computer system, shared memory pool, or task is different because the memory management table and task interface are the same. This makes it easy to achieve highly reliable memory management.

FIG. 5 is a flowchart for explaining the memory release test in detail, and FIG. 6 is a flowchart for explaining the memory access test in detail.

DESCRIPTION OF SYMBOLS 1...Memory management means, 2...Memory management table, 21...Entry number cell, 22...Memory status table, 221...Memory ID item, 222...Task ID item, 223 ...Memory size item.

Claims (1)

[Claims] In a portable shared memory management method for a computer system in which multiple tasks that use memory on a shared memory pool exclusively and temporarily operate simultaneously, the allocation state of the shared memory is determined independently of the computer system and the shared memory pool. and a memory management table that stores an allocated memory size, and a task interface independent of the computer system and the task, which operates the memory management table according to requests from the task, and allocates memory on the shared memory pool. A portable shared memory management system, comprising a memory management means for managing the state and checking the validity of reading, writing, and releasing data into the memory.