JPS637581A - File managing device - Google Patents

Abstract

PURPOSE:To improve a responsiveness by copying a relevant file in the successive blocks of a disk before using as for the file requiring successive physical blocks. CONSTITUTION:A successive block managing device 31 decides whether the file requires the successive physical block or not by a successive block using flag 32 in the node of an ordinary file, copies the file in the successive area 33 maintained in a successive block part 30 before the use of the file, and manages information such as a leading physical block. At the time of making access to the file, a successive block managing device 31 is related to perform a processing to the successive area 33, when the use of the file is completed, if there is a writing to the file, the information is recopied to an original physical block indicated by a disk block address 11. Thereby, an overhead by a disk access through an indirect addressing can be reduced and an effect to a real time characteristic is large.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of Industrial Application The present invention relates to a disk file management device, and for programs that require real-time performance, by allocating contiguous areas of physical blocks on the disk, The present invention relates to a file management device that improves responsiveness by reducing the overhead of disk access when loading necessary blocks.

Conventional technology FIG. 2 shows a file management device for managing a conventional hierarchical file system, which includes a disk 1, a user management device 6,
It is composed of a node management device 7.

Disk 1 is divided into four parts. That is, a boot block 2 stores programs used during booting, and a super block 3 stores information regarding the entire file system such as disk block size.
, a node list section 4 in which physical addresses of files and directories are recorded, and a data section 5 in which files and directories are stored. Here, the nodes that are the constituent elements of the node list section 4 are shown in FIG. Each node includes a node number 10 and 13 disk block addresses 11. The first 10 directly point to the first 10 blocks of the file. The 11th is indirect block 1
2, and its indirect block 12 contains 128 subsequent block addresses of the file. Further, the 12th address indicates the address of the double indirect block 13, and the 12th address of the double indirect block 13 indicates the addresses of up to 128 indirect blocks 12. Similarly, the 13th address indicates the address of the triple indirect block 14. The triple indirect block 14 indicates the address of up to 128 double indirect blocks 13.

The node management device 7 in FIG. 2 manages active nodes in the node list section 4. The user management device 6 manages the users in use, and a current directory pointer 8 therein points to a node of the current working directory on the file system. Items stored in the data section 6 include data files and a directory file 20 (FIG. 4).

The directory file 20 is composed of a node number 1o and a file name 21 pair.

The operation of the conventional hierarchical file system file management device configured as described above will be explained.

When searching for a file, use the path salt of the file system's directory directory %IJ-. To access a file by starting from a certain node, such as the current working directory, and reading the directory file, searching for the next component of the path salt, and obtaining the node of the last component of the path salt. becomes possible.

Problems to be Solved by the Invention However, in the above-mentioned file management device, if the file is larger than 10 physical blocks, the latter part of the file cannot be accessed directly, and the file must be accessed up to four times. There will be blocks that require disk access. Therefore, in applications where real-time performance is required to a certain extent or more, overhead due to disk access occurs when loading necessary blocks, which is not efficient.

In view of this, it is an object of the present invention to provide a file management device that makes it possible to reduce the overhead caused by disk access during loading for programs that require real-time performance in file systems.

Means for Solving the Problems The present invention provides a means for managing physical block addresses of files and directories in a hierarchical file system of a disk, a means for indicating the current working data (IJ), and a means for indicating the physical block address of a data file on a disk. means for indicating whether or not a contiguous block area is required; means for managing concatenated physical blocks on a disk; and continuous physical blocks on the disk.

This is a file management device equipped with means for ensuring security.

Effect: With the above-described configuration, the present invention can improve responsiveness to files that require continuous physical blocks by copying the files to a continuous block area of the disk before use. can.

Embodiment FIG. 1 shows a file management device in an embodiment of the present invention. It is composed of a disk 1, a user management device, etc., a node management device 7, and a continuous block management device 31. Disk 1 is divided into five parts. That is, a boot block 2 stores programs used at boot time, a super block 3 stores information about the entire file system such as the size of disk blocks, and records the physical addresses of files and directories. They are a node list section 4, a data section 5 in which files and directories are stored, and a continuous block section 30 for securing a continuous area of physical blocks. In addition to the disk block address 11 and node number 10 shown in FIG. 3, the nodes that are components of the node list section 4 include a flag indicating whether to use continuous blocks for nodes of files other than directory files. is attached. Further, the node management device R7 manages active nodes in the node list section 4. The user management device 6 manages the users in use, and the current working directory pointer 8 therein points to the node of the current working directory on the file system. Items stored in the data section 6 include normal files and a directory file 2o (Figure GA).

The directory file 2o is composed of a node number 10 and a file name 21 pair. Further, the continuous block management device 31 determines whether or not the file requires continuous physical blocks based on the continuous block use flag 32 in the node of the normal file, and reserves them in the continuous block unit 30 before using the file. The file is copied to the continuous area 33, and information such as its first physical block is managed.

The operation of the file management device of the hierarchical file system configured as above will be explained. From the path name of the file you want to access from the current working directory, trace the nodes of the directory and obtain the node number of the file. Then, the status of the continuous block usage flag 32 in the node of the file is checked. If the continuous block use flag is off, there is no need to copy the file to the continuous block area, and disk access to the file uses disk block address 11 in the node as in the conventional example. When the continuous block use flag 32 is on, the continuous block management device 31
A continuous area 33 is secured in the continuous block section 3o of the disk, and before using the file, the file is copied to the secured continuous area 33 based on the information of the disk block address 11 of the node of the file, and the continuous area 33 is It manages information regarding the area 33. Thereafter, when accessing the file, the continuous block management device 31 is involved and processes the continuous area 33. When the use of the file is finished, if there is any writing to the file, the data is copied back to the original physical block indicated by the disblock address 11.

According to the above device, files that require high responsiveness can be copied to a contiguous physical block area, eliminating the overhead of disk access caused by indirect addressing and meeting real-time requirements. I can answer.

Effects of the Invention The present invention provides a means for managing physical block addresses of files and directories, a means for indicating the current working directory, and a method in which files require a contiguous area of physical blocks on the disk in the disk hierarchical file system. By providing a means for indicating whether or not to use a disk, a means for managing contiguous physical blocks on the disk, and a means for securing contiguous physical blocks on the disk, the overhead caused by disk access due to indirect addressing can be reduced, and real-time It has a great effect on sex.

[Brief explanation of drawings]

Fig. 1 is a block diagram of a file management device according to an embodiment of the present invention, Fig. 2 is a block diagram of a conventional file management device, Fig. 3 is an explanatory diagram of file access by a node, and Fig. 4 is a pointer). It is an explanatory diagram of a file. 1...Disk, 2...Put block, 3...Super block, 4...
Nodo list part, 6・Pa...data part, 6...
User management device, 7... Node management device, 8.
...Pointer to current working directory, 9...
...Node, 1o...Node number, 11゛・
...Disk block address, 12...
Indirect block, 13...Double indirect block, 1°
4... Triple indirect block, 20... Directory file, 21... File name, 3
0...Continuous block section, 31...Continuous block management device, 32...Continuous block use flag, 33...Continuous area.

Claims (1)

[Claims] In a hierarchical file system of a disk, a means for managing physical block addresses of files and directories, a means for indicating the current working directory, and a means for indicating whether a file requires a contiguous area of physical blocks on the disk. A file management device comprising: means for managing continuous physical blocks on a disk; and means for securing continuous physical blocks on the disk.