JPH02245958A - Buffer control system - Google Patents

Abstract

PURPOSE:To facilitate the specification of a trouble inducing module by providing an acquired module identifier storage part and an in-use module identifier storage part. CONSTITUTION:Each of plural buffers 111n is provided with the acquired module identifier storage part where the identifier of an optional module 113i which makes a request to use the buffer 111j is stored and the in-use module identifier storage part wherein the identifier of an optional module 113i which uses the buffer 111j currently or another optional module 113k is stored. Then when plural modules 113m perform processes respectively while using plural modules 111n, buffer control is carried out by using acquired module identifiers and in-use module identifiers. Consequently, the retrieval of a faulty module in buffer use is facilitated.

Description

[Detailed Description of the Invention] (Table of Contents) Overview Industrial Field of Application Conventional Technology Problems to be Solved by the Invention Means for Solving the Problems Action Example ■, Structure of the Example ■, Operation of the Example ■ , Summary of Examples■0 Variations of the Invention Effects of the Invention [Summary] Regarding a buffer management method in which buffer usage is controlled by a common buffer management unit, the purpose of this invention is to facilitate the identification of failure-causing modules, and to Buffers, multiple modules that each use a different buffer among the multiple buffers, a common buffer management unit that has a module buffer management area that exists in each module, and buffer management that supports buffer acquisition requests from any module. a common buffer management processing unit configured to set data, release the allocated buffer in accordance with a release request from a module using the allocated buffer, and update buffer management data corresponding to the release request in a module buffer management area corresponding to the acquisition request; Each of the plurality of buffers includes an acquisition module identifier storage section that stores the identifier of the module that has requested the use of the buffer, and an in-use module identifier storage section that stores the module identifier of the module that is currently using the buffer. Equipped with.

[Industrial application field]

The present invention relates to a buffer management system, and for example, to a buffer management system in which buffer usage is controlled by a common buffer management unit in buffer management in a data communication device.

Currently, data communication by computers is becoming faster and the memory area for data transmission and reception is increasing. As a result, buffer management for data transmission and reception has become complicated, causing failures.

[Conventional technology]

When the common buffer management unit allocates buffers used by each program in a modular structure.

The module identifier of the module in use is set in the control area of each buffer.

[Problem to be solved by the invention]

By the way, in the above-mentioned conventional method, especially when another module continues to use a buffer acquired by an arbitrary module, failures such as non-release of buffer or double release of buffer may occur. be.

In this case, we did not store information such as which module acquired the buffer, which module did not free the buffer, or which module attempted to free the buffer twice. However, there was a problem in that it was not possible to identify the location of the failure.

The present invention was created in view of these points, and an object of the present invention is to provide a buffer management method that facilitates the search for a faulty module when using a buffer.

[Means for Solving the Problems] FIG. 1 is a block diagram of the principle of the buffer management system of the present invention.

In the figure, each of the plurality of buffers 111 includes
Any module 1 that made a request to use the buffer
13. and any module 113 currently using the buffer. or any other module 113. There is an in-use module identifier storage section that stores the identifier of the module.

A plurality of modules 113. is a plurality of buffers 111f
A different buffer is used for each of i.

Multiple module buffer management areas 115. has a plurality of modules 113. Buffer management data corresponding to the buffer is provided for use in the buffer and exists in the common buffer management unit 117.

The common buffer management processing unit 119 is an arbitrary module 1.
Setting of buffer management data in response to a request to acquire one or more buffers 111J by 13□, allocated buffer 1
Any module using 113.11j. Alternatively, in accordance with a release request from another module 113, the allocated buffer 111 is released and the buffer management data corresponding to the release request is updated in the module buffer management area 1151 corresponding to the acquisition request.

Therefore, as a whole, in a data processing device in which each of a plurality of modules performs respective processing using a plurality of buffers, buffer management is performed using the acquired module identifier and the currently used module identifier. The present invention is constructed.

[For production]

Any module 113i is the common buffer management processing unit 1
19 and n buffers 111. When a request is made to use one or more of the percentages, the common buffer management processing unit 11
9 checks whether the number of buffers 111j requested by the module 113z can be allocated from the information in the module buffer management area 115i corresponding to the module 1131, and if allocated, stores the acquired module identifier of the buffer 111j. The module identifier of the module 113i is set in the section and in-use module identifier storage section. Furthermore, module buffer management area 115. Buffer management data such as an empty buffer is set in , and the starting address of the allocated buffer 111j is notified to the module 1135.

The data in the buffer 111j is transferred to the module 11
When used by another module 113 (f is a number less than or equal to n and other than i) following the processing of 3i, the module 113. passes the start address of the buffer 111 to another module 113L. Module 113 for subsequent processing. sets the module identifier of the module 113 in the in-use module identifier storage section of the buffer 111°.

When releasing the buffer 111j in use, the module 113 using the buffer 111j instructs the common buffer management processing unit to release the buffer 111. requesting the release of Upon receiving the request, the common buffer management processing unit 1
19 initializes the data in the acquisition module identifier storage section and the in-use module identifier storage section of the buffer 111j, and the module 1 that acquired the buffer 1llJ
13, module buffer management area 115. Update buffer management data.

In the present invention, the acquisition module identifier storage section and the in-use module identifier storage section make it easy to identify the fault-inducing module.

〔Example〕

Hereinafter, embodiments of the present invention will be described in detail based on the drawings.

FIG. 2 shows the configuration of a buffer management system in an embodiment of the present invention, FIG. 3 shows an explanation of the buffer, and FIG. 4 shows an explanation of the module buffer management area.

(1) Here, the correspondence between the embodiment of the present invention and FIG. 1 will be shown.

Buffer 1117 is buffer 227 . ~227, corresponds to.

Module 113. are modules 2111 to 227,
corresponds to

Module buffer management area 115. is the module buffer management area 241. ~241. corresponds to

The common buffer management unit 117 is the common buffer management unit 22
It corresponds to 5.

The common buffer management processing section 119 corresponds to the common buffer management processing section 213.

In FIG. 2, the data processing device to which the buffer management method is applied has three modules 211 . ．． 211□ and 2113, a common buffer management processing section 213, and a buffer management section 221.

Note that three modules 211. ~211. The common buffer management processing unit 213 includes three modules 2111 to 2111.
2113 and a ROM that stores a processing program for the common buffer management processing unit 213, and a CPU (not shown) that executes the processing program. The buffer management unit 221 used for processing by the common buffer management processing unit 213 is a RAM (not shown).
and is connected to the CPU via a bus (not shown).

The buffer management unit 221 includes a data storage area 223 that stores data, and a common buffer management unit 225 that is used by the common buffer management processing unit 213 in buffer allocation and the like and stores buffer management data and the like.

Nine buffers 227 . ~227. is data storage area 2
23, starting with buffer 227I and buffer 227
9 are sequentially arranged in the address space. Also, the third
As shown, buffer 227. is buffer 227
Modules 2111 to 2113 that made the acquisition request for 1
Acquisition module identifier storage area 229 that stores the identifier of one of the modules. , a used module identifier storage area 23i that stores the identifier of one of the modules 2111 to 211° currently using the buffer 2271, and a used flag 2331 indicating that the buffer 2271 is currently in use, and data stored therein. data section 235. Consists of. In addition, buffers 227□ to 227
Although the configuration of buffer 9 is not shown, it is similar to buffer 2271.

In addition, the in-use flag 233. ~233. value is “ON”
When , the buffer 227 is in use, and when it is not "ON", it is not used.

The common buffer management unit 225 includes a total buffer number area 237 that stores the number of nine buffers 227, a buffer start address storage area 239, and three modules 2111.
~211. Buffers 227 allocated to each of
1-227. Three module buffers to manage! Science 241. ~2413.

As shown in FIG. 4, module buffer management 1241
+ indicates the total buffer number area 2431 indicating the number of buffers 227 allocated to the module 2111, the module 211. Empty buffer number area 24 indicating the number of unused buffers 227 among the buffers 227 allocated to
5. , buffer 2 allocated to module 2111
Available buffer start address storage area 2471.24 indicating the start address of 27. Module 2111 Buffer 2 that is not used among the allocated buffers 227
Empty buffer address storage area 249 indicating address 27
□ and module 211. Buffer 2 used by
27. Used buffer address storage area 251.27 indicating the first address. Consists of.

Furthermore, module buffer management areas 2412 and 2413
Although the configuration of the module buffer management area 24 is not shown,
The configuration is similar to No. 11.

The operation of the buffer management method of the n-needle one-piece embodiment is as follows:
The buffer acquisition operation, buffer movement operation, and buffer release operation will be explained separately. Note that the module 211. ~2
11. The module identifiers are r1'', r2'', and
r3".

When the power of "iXr" is turned on, the common buffer management processing unit 213 first initializes the buffer management unit 221 and assigns each module 211. Buffer 2 used by 211
271-227. Assign. Here, the buffers used by the module 2111 are three buffers 227,
~227, and the buffers used by the module 211□ are three buffers 2274~227. Binding, module 211. The buffers used by 3 buffers 227
7-227. shall be.

Next, the common buffer management processing unit 213 sets buffer management data in the three module buffer management areas 2411 to 2412. Buffer total number area 2431-243.
are each set to ``3'', and each of the free buffer number areas 245. to 245. is set to ``3''.

In addition, the common buffer management processing unit 213
7, ~227. are concatenated in order and the address of the first buffer 2271 is used as the usable buffer first address storage area 247. Set to .

Similarly, buffers 2274-227. are concatenated in order and the address of the first buffer 2274 is set in the usable buffer first address storage area 247□, and then the buffer 227 . ~227. are concatenated in order and the address of the first buffer 2277 is set in the usable buffer first address storage area 247.

Further, the common buffer management processing unit 213 stores the empty buffer address storage area 249. Set the address of the buffer 2271 to . Similarly, empty buffer address storage area 249□
The address of the buffer 2274 is set in the empty buffer address storage area 249, and the address of the buffer 2277 is set in the empty buffer address storage area 249.

Buffers 2271-227. Since none of them are used, the common buffer management processing unit 213 stores the used buffer address storage area 251. -251, the initial state is set.

j buffer '6 Next, when the buffer management unit 221 is in the state (i) mentioned above, the module 2111 manages the two buffers 227
The following is an example of a case where the use of . FIG. 5 shows an explanation of the buffer acquisition operation.

Module 211. Since it becomes necessary to use two buffers, the module identifier "rl" and the number of buffers to be acquired "°2"°, which are information necessary for buffer acquisition, are sent to the common buffer management processing unit 213 (step 411). Upon receiving the acquisition request, the common buffer management processing unit 213
First, it is checked whether the request is valid (step 413).

If the request is valid, the common buffer management processing unit 2
13 specifies which module is the module that made the request based on the module identifier "rl". In step 415L, the empty buffer number area 245. (step 417).

It is checked whether there are enough buffers to satisfy the request (step 419), and if the request is satisfied, the empty buffer address storage area 249. Buffer 2 stored in
27. The addresses of the buffers 227I and 227□ connected to the buffers 2271 are acquired (step 421), and their acquired module identifier storage areas 229. ．． 229□ and used module identifier storage area 231. and 231. "rl" is set in the in-use flag 233 and 233□ (step 423), and "'ON" is set in the in-use flag 233 and 233□ (step 4
25).

Next, the common buffer management processing unit 213
1. The module buffer of M2411 is reset (step 427). Through this process, the empty buffer number area 245. becomes II I II, the empty buffer address storage area 249I becomes the address of the buffer 227, and the used buffer address storage area 251. The address of the buffer 2271 is set in . It should be noted that other buffer management data of the module buffer management area 2411 is a buffer total number area 243I and an available buffer start address storage area 247. The value of is not changed.

After this, the common buffer management processing unit 213
At step 429), the module 2111 passes the address of the buffer 227, which is the first buffer, to the Balanoa 227.111. and 2272.

Note that if the buffer acquisition request is invalid, the module 211. An error notification is given to (step 431). Furthermore, if there is no buffer sufficient to satisfy the -1 acquisition request, the common buffer management processing unit 213
1+ is notified of this (step 433).

One ← Chuuyu, hey! - If the dynamic IU buffer management unit 221 is in the state (ii),
Module 211. The data stored in buffer 1227 and 227t used by module 211.
The buffer movement operation when used by the module 211□ that performs processing subsequent to the above will be explained.

At this time, module 211. The buffer 227. is in the module 211□. The address is passed and the stored data is not copied. Buffer 227. When the address of the module 211z is passed, the module 211z uses the used module identifier storage area 231 and the address of the module 21
1 Set the module identifier “r2” for buffer 2
Processing is performed using the data of 271 and 227□.

Module 211! After processing, further module 211,
uses data in buffers 227I and 227□, then module 211□ uses data in buffers 227I and 227□. Pass the address of buffer 2271 to . Buffer 2271
When the address of module 211. sets the module identifier "r3" of the module 211 in the used module identifier storage areas 2311 and 231□.

iv) The operation of the module 2113 to release the buffer when the buffer management unit 221 is in the state (iii) will be described. FIG. 6 shows an explanation of the buffer release operation.

Module 211. are in use buffers 2271 and 2
When requesting the release of 27□, the module 211
3 sends the address of the buffer 2271, which is the first buffer in use, to the common buffer management processing unit 213 (step 511).

The common buffer management processing unit 213, which has received the address of the buffer 2271, first checks the X version of the sent buffer address (step 513). If the buffer address is one that exists, then the in-use flag 233. of the buffer 227I is used to prevent double freeing of the buffer. is set to "ON" (step 515). If the in-use flag 233. is set to "ON", the acquisition module identifier storage area 229. Module identifier “rl” stored in
If "r1" exists, the buffer 227 is checked from the module identifier.
Step 519) identifies the module that made the acquisition request of module 211.1 that made the acquisition request. module buffer management area 241. Search for (step 521) Ubuffer 227. address of buffer 22
The buffer 227 requested to be released from the module 2113 based on the connection information of 7 and the connection information of Balanoa 227□
is the buffer 227. and 227□, and these acquisition module identifier storage areas 229. ．． 22
9□ and used module identifier storage areas 2311 and 231□ are initialized (step 523), and in-use flags 2331 and 233□ are also initialized (step 5).
25).

Next, the common buffer management processing unit 213
The module buffer management area 2411 of No. 11 is reset (step 527). By this process, the empty buffer number area 245. becomes "3", and the in-use buffer address storage area 2511 is initialized. Also, the buffer 22
7I is the buffer 227. is concatenated after. Note that the total number of buffers area 243 . is other buffer management data in the module buffer management area 2411 . ．． Available buffer start address storage area 247. and empty buffer address storage area 249. The value of is not changed. After that, the common buffer management processing unit 213 notifies the module 2113 that the buffer release process has been successfully completed (step 52
9).

Note that if the buffer release request is invalid, the module 211. An error notification is sent to the buffer 227. (step 531). In-use flag 233. is “ON”
”, an error notification is also given (step 533).Furthermore, the acquisition module identifier storage area 229
An error notification is also given if the module identifier stored in 1 does not exist (step 535).
.

(2) At the end of this example, by storing the module identifiers of the module that acquired the buffer and the module that is using the buffer, it becomes easy to identify the module that causes the failure.

Note that in the embodiment of the present invention described above, the number of processing modules is three, but the number is not limited to this.

Further, although the number of buffers 227 is nine, it is not limited to this.

Furthermore, in ``correspondence between examples and FIG. 1'',
Although the correspondence between the present invention and the embodiments has been described, those skilled in the art can easily imagine that the present invention is not limited to this and that there are various modifications 1M.

〔Effect of the invention〕

As described above, according to the present invention, it becomes easy to identify the module responsible for a buffer management failure, which is extremely useful in practice.

[Brief explanation of drawings]

FIG. 1 is a principle block diagram of the buffer management method of the present invention, FIG. 2 is a block diagram of the configuration of the buffer management method according to an embodiment of the present invention, FIG. 3 is an explanatory diagram of the data storage area, and FIG. The figure is an explanatory diagram of the module buffer management area, FIG. 5 is an operation flowchart for buffer acquisition, and FIG. 6 is an operation flowchart for buffer release. In the figure, 111.227 is a buffer, 113.211 is a module, 115.241 is a module buffer management area, 117.
225 is a common buffer management unit, 119, 213 is a common buffer management processing unit, 221 is a buffer management unit, 223 is a data storage area, 229 is an acquisition module identifier storage area, 231 is a used module identifier storage area, 233 is an in-use flag , 235 is a data section, 237 is a total buffer number area, 239 is a buffer start address storage area, 243 is a buffer total number area, 245 is an empty buffer number area, 247 is a usable buffer start address storage area, 249
is an empty buffer address storage area 9.25 is a used buffer address storage area. Ba-7a, lwhip, light 3rd figure
Figure Buff yJ Motion ear movement diagram Me e 'ECi4

Claims (1)

[Claims] (1) A plurality of buffers (111_n) (n is a natural number), and a plurality of modules (113_m) each using a different buffer among the plurality of buffers (111_n).
(m is a natural number); a common buffer management unit (117) having a plurality of module buffer management areas (115_m) that exist corresponding to the plurality of modules (113_m) and store buffer management data; Any one or more of the buffers (111_j) by the module (113_i) (i is a number less than or equal to m)
Setting of the buffer management data corresponding to the acquisition request (j is a number less than or equal to n), the arbitrary module (113_i) using the allocated buffer or the other module (113_i)
113_k) (where k is a number less than or equal to m and other than i), the allocated buffer is released and the buffer management data corresponding to the release request is updated in the module buffer management area (115_i) corresponding to the acquisition request. a common buffer management processing unit (119); and acquisition module identifier storage for storing an identifier of the arbitrary module (113_i) that has made a request to use the buffer (111_j) in each of the plurality of buffers (111_n). and an in-use module identifier storage unit that stores an identifier of the arbitrary module (113_i) or other arbitrary module (113_k) currently using the buffer (111_j). buffer management method.