JP3037113B2 - Split type sequential knitting file device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a split type sequential knitting file device, and more particularly to a split type sequential knitting file device capable of efficiently removing garbage at regular intervals.

[0002]

2. Description of the Related Art A file of a division type sequential organization is suitable for storing a relatively small number of files as members as many as a program library, and is efficiently used.

[0003] That is, a file of the split type sequential composition is composed of a plurality of members each in the form of a sequential composition file, and the members are accommodated in the member entity part in the order of creation, and the members are named using the member name as a key. The storage location is recorded in the directory section.

[0004] Addition, updating, and deletion of members to such a divided sequential file will be described.

When a new member is added to a divided sequential file, the member is stored in the member entity in the order of creation after the last member among the existing members with reference to the directory part. At the same time, the name of the added member and its storage position are registered in the directory section.

When updating the contents of an existing member,
First, the member whose contents have been updated is stored in the member entity from the next member after the last member among the existing members with reference to the directory, and the corresponding member name in the directory is determined based on the storing position. The old storage position recorded in the new storage position is changed to the new storage position. Do not change the member name. For this reason, the old member entity before update at the old storage position of the member entity part remains in the file as invalid data that is never read again.

When deleting an existing member, only the member name of the directory part and its storage position are deleted.
For the member entity to be deleted in the member entity part,
As in the case of the old member entity to be updated, the invalid data remains in the file as invalid data that is never read again.

[0008] As described above, when updating or deleting a member of a divided sequential file, the previously registered member entity becomes invalid, the member area remains as garbage, and the memory is effectively used. There was a problem that can not be.

Therefore, conventionally, every time a member is added or updated, the garbage of the divided sequential file is usually deleted as necessary so that the user is not aware of the garbage. there were.

In order to solve the burden on the user, when updating a member, the member to be updated is first deleted, and then the remaining members in the file are condensed (repacked from the head of the member substantial part). Japanese Patent Application Laid-Open No. 58-163054 discloses a method in which garbage is deleted by adding a member whose contents have been updated.

[0011]

In the above-described garbage deletion system which is performed by the user of the conventional divided type sequential file system, the user must always know the garbage state of the divided type sequential file system. However, there is a disadvantage that a great burden is imposed on the user.

Further, in the divided type sequential file system garbage deletion system described in Japanese Patent Application Laid-Open No. 58-163054, which is performed every time updating, the inconvenience caused by garbage caused by member deletion when a member is added cannot be avoided.
When a member is added, the file member must be condensed, which degrades the performance of updating and adding members.

An object of the present invention is to store files in which members have been updated and deleted, and to perform garbage deletion on these files at regular intervals, so that the memory can be efficiently used in a divided type order. An object of the present invention is to provide a knitting file device.

[0014]

According to a first aspect of the present invention, there is provided a split-type sequential knitting file apparatus which stores a plurality of split-type sequential knitting files, and a split-type sequential knitting file stored in the file storing means. File editing processing means for updating and deleting and adding members constituting the file, garbage file storing means for storing an identifier of a file having a garbage by updating or deleting members by the file editing processing means, and the garbage file Garbage deleting means for periodically deleting the garbage of the file corresponding to the file identifier stored in the storage means.

According to a second aspect of the present invention, there is provided the split type sequential knitting file device according to the first aspect of the invention.
The garbage file storage means is characterized in that members are updated or deleted, and the identifier of a file having garbage is stored as a queue.

[0016]

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of a split type sequential knitting file apparatus according to the present invention.

As shown in FIG. 1, the split type sequential knitting file apparatus according to the present embodiment has a split type sequential knitting file (Par).
titrated Access Method Fi
le, abbreviated as PAM file), a PAM file edit processing unit 1-1 for adding, updating, and deleting processes;
A garbage deletion unit 1-2 that performs garbage deletion processing, ie, a garbage deletion unit 1-2 that performs garbage deletion processing, and a garbage file that stores a file that has undergone member update and deletion processing, that is, a file with garbage. Queue section 1-3 and a plurality of PAM file sections 1-4
It is comprised including.

The PAM file section 1-4 stores a member entity section 1-4-2 storing the substance of the members stored in this file, the names of the stored members, and the member names. It is configured to include a directory section 1-4-1 that stores the start address S and end address E of the member entity section 1-4-2.

PAM of PAM file edit processing section 1-1
The addition, update, and deletion of members to the file unit 1-4 will be described.

To add a new member to the PAM file section 1-4, refer to the directory section 1-4-1.
The members are stored in the member entity part 1-4-2 in the order of creation from the last member of the existing members. At the same time, S and E indicating the name of the added member and its storage position are registered in the directory section 1-4-1.

When updating the contents of an existing member,
First, the members whose contents have been updated are stored in the directory section 1-4.
-1 is stored in the member entity section 1-4-2 from the end of the last member among the existing members, and the corresponding member in the directory section 1-4-1 is stored based on the storing position. Change the old storage location recorded in the name to the new storage location. Do not change the member name. Therefore, the member entity 1
The old member entity before update at the old storage location of -4-2 is
The invalid data that is never read out remains in the file. The file name whose member has been updated is stored in the garbage file queue section 1-3.
And are queued.

When deleting an existing member, only the member name of the directory section 1-4-1 and its storage position are deleted. For the member entity to be deleted in the member entity section 1-4-2, As in the case of the old member entity to be updated, the invalid data remains in the file as invalid data that is never read again. In addition,
The file name from which the member has been deleted is sent to the garbage file queue section 1-3 and queued.

The garbage file queue section 1-3 is a PA
The member supplied from the M-file editing unit 1-1 queues the updated or deleted file name, and removes the garbage-deleted file name from the queue.

The garbage deletion unit 1-2 is activated at regular intervals, refers to the garbage file queue unit 1-3, and refers to the directory unit 1 of the PAM file unit 1-4 corresponding to the file name stored therein. -4-1,
Repack members and remove garbage.

FIG. 2 is a flowchart showing the editing processing operation of the PAM file editing processing section 1-1, and FIG. 3 is a garbage deleting section 1.
13 is a flowchart showing the operation of a garbage deletion process of -2.

The update processing operation and the garbage deletion processing operation of the present embodiment will be described with reference to FIGS.

Referring to FIG. 1, first, the general operation of the present embodiment will be described.

In accordance with the user's instruction, the PAM file editing processing section 1-1 performs editing processing such as adding, updating, and deleting members to the file in the PAM file section 1-4 that stores the file specified by the user. In the case of updating and deleting members, the file names subjected to these processes are queued in the garbage file queue section 1-3.

At regular time intervals, the garbage deleting unit 1-
Reference numeral 2 denotes a PAM corresponding to the file name queued in the garbage file queue section 1-3 with reference to the garbage file queue section 1-3.
The garbage is deleted from the file section 1-4. In this manner, the PAM file section 1-4 performs the garbage deletion process periodically and only for the queued file, thereby not burdening the user and in a shorter time than before. The garbage can be deleted, and the PAM file unit 1-
4 can be efficiently used.

Initially, as shown in FIG. 2, the PAM file section 1-4 stores n member entities having member names 1 to n in the member entity section 1-4-2 so that no garbage area exists. Each storage location can be known by the directory section 1-4-1 in which the start address S and the end address E of the storage location are stored corresponding to each member name. it can.

Next, the member update processing operation of the PAM file editing processing section 1-1 during the editing processing operation will be described in detail with reference to FIG.

The PAM file edit processing section 1-1 stores a file specified by the user in a PAM file section 1-4.
(Step 1). As an example of the update request, a request for updating the member 3 of the file a to the new member 3 whose contents have been updated will be described.

Next, the PAM file editing processing section 1-1
Refers to the last address of each member of the directory section 1-4-1 and adds a new member 3 having the updated content after the member having the highest address value (in this case, member n) to the member entity section 1-. 4-2 is stored at the position of the double frame (step 2).

Next, the storage position corresponding to the member 3 in the directory section 1-4-1 is rewritten to the start address S and the end address E which are the storage positions of the new member 3 stored in step 2 (corresponding to the old address). The position of the new address is indicated by a dotted arrow, and the position corresponding to the new address is indicated by a thick arrow (step 3).

By doing so, the entity of the member 3 previously stored will be invalid data that cannot be read out again, that is, will be garbage and will remain in the file a. This is indicated by hatching).

Next, the PAM file editing processing section 1-1
Queues the updated file name a in the garbage file queue section 1-3, stores the fact that the file becomes the target file for the garbage deletion processing, and ends the member update processing operation (step 4). . At this time, if the same file name has already been queued, the file name is not queued.

Next, the garbage deletion processing operation of the garbage deletion unit 1-2 will be described in detail with reference to FIG.

As an example of the garbage deletion processing operation, a case will be described in which the garbage generated by updating the member 3 of the file a is deleted. The PAM file section 1-4 before the deletion processing is shown on the lower left side of FIG. 3 (the garbage area is indicated by hatching), and the PAM file section 1 after the deletion processing is shown.
-4 is shown on the lower right side of FIG.

The garbage deleting unit 1-2 is periodically started by a built-in timer, performs a garbage deleting process described below, and starts the timer when the garbage deleting process ends.

The timer starts the garbage deletion processing operation of the garbage deletion unit 1-2 after a predetermined time has elapsed after the start (step 21).

The garbage deletion unit 1-2 successively reads the names of the files queued in the garbage file queuing unit 1-3 (files in which member update or deletion processing has been performed) (step 22). The garbage deletion processing operation described below is performed.

The garbage deleting section 1-2 checks the directory section 1-4-1 of the PAM file section 1-4 and obtains the garbage area from the start address of the garbage area, that is, the last address E of the member 2 in FIG. Subsequent member entities (the entities of the double frame, members 4 to n, and member 3) are copied from the start address of the garbage area (step 23).

Next, the start address S and the end address E of each member of the directory section 1-4-1 are stored in step 23.
Is rewritten to the start address S and end address E of the entity of each member as a result of the copy performed in step (step 24).

Since the garbage has been deleted, the garbage deletion processing operation is completed, the timer is started, and the garbage deletion processing operation is prepared (step 25).

If there are several garbage areas and the addresses are not continuous, steps 23 and 24 are executed.
Is repeatedly performed for each of the several garbage areas.

As described above, the divided sequential knitting file device according to the present embodiment periodically performs garbage deletion processing of a file having garbage, so that the user does not need to consciously delete the garbage. The burden on the user can be significantly reduced.

Further, by storing the file names of the files whose members have been updated and deleted, and referring to the file names to perform garbage deletion processing only on those files, the garbage deletion processing can be shortened efficiently. Can be done in time.

Since the garbage deletion process is performed periodically, the performance of the normal operation such as the file update process is not affected.

[0050]

As described above, the divided sequential knitting file device of the present invention periodically deletes garbage of a file having garbage, so that the user does not need to consciously delete garbage. This has the effect that the burden on the user can be significantly reduced.

Further, by storing the file names of the files whose members have been updated and deleted, and referring to the file names to perform garbage deletion processing only on those files, the garbage deletion processing can be shortened efficiently. It has the effect that it can be done in time.

Further, since the garbage deletion processing is performed periodically, there is an effect that the performance of the file update processing which is a normal operation is not affected.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an embodiment of a split type sequential knitting file device according to the present invention.

FIG. 2 is a flowchart showing an example of an operation of a PAM file editing processing unit 1-1 in the division type sequential composition file device of the present embodiment.

FIG. 3 is a flowchart showing an example of the operation of the garbage deleting unit 1-2 in the divided sequential knitting file device of the present embodiment.

[Explanation of symbols]

 1-1 PAM file edit processing unit 1-2 Garbage deletion unit 1-3 Garbage file queue unit 1-4 PAM file unit 1-4-1 Directory unit 1-4-2 Member entity unit

────────────────────────────────────────────────── ─── Continuation of the front page (56) References JP-A-1-226049 (JP, A) JP-A-4-148247 (JP, A) JP-A-5-324419 (JP, A) JP-A-5-324419 35552 (JP, A) (58) Fields investigated (Int. Cl. ⁷ , DB name) G06F 12/00

Claims (2)

(57) [Claims] 1. A file storing means for storing a plurality of divided sequential files, a file editing processing means for updating, deleting and adding members constituting the divided sequential files stored in the file storing means. A garbage file storage means for storing an identifier of a file having a garbage in which members are updated or deleted by the file editing processing means, and a garbage of a file corresponding to a file identifier stored in the garbage file storage means is periodically updated. And a garbage deleting means for sequentially deleting. 2. A divided sequential knitting file apparatus according to claim 1, wherein said garbage file storage means stores, as a queue, an identifier of a file having garbage by updating or deleting a member.