KR20170130180A - Method and Apparatus for Processing Data Using Non-Volatile Memory - Google Patents

Abstract

Disclosed are a data processing apparatus using a nonvolatile memory and a method thereof. According to an embodiment of the present invention, the data processing apparatus improves data processing speed by using nonvolatile memory separately storing metadata of data. The data processing apparatus comprises: a nonvolatile memory; a memory; and an application execution part.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a non-volatile memory,

The present embodiment relates to an apparatus and method for processing hybrid data using a nonvolatile memory.

The contents described in this section merely provide background information on the present embodiment and do not constitute the prior art.

1 is a diagram illustrating a process of an existing data processing apparatus for processing data.

The application execution unit 110 makes an open request to the file system 113 (S120). In order to execute a write command or a read command with respect to certain data, an existing data processing apparatus makes an open request for the corresponding data and requests the meta data of the data.

The file system 113 requests the retrieval of the metadata of the corresponding data according to the request (S125). When the file system 113 receives an open request for specific data from the application execution unit 110, the file system 113 interprets the open request as a request for retrieving the metadata of the corresponding data. Accordingly, the file system 113 requests the storage device 116 to retrieve the metadata of the corresponding data.

The storage device 116 searches the meta data according to a search request of the meta data of the corresponding data, and transmits a search completion message of the meta data (S130). When the storage device 116 receives a request for retrieving the metadata of the corresponding data from the file system 113, the storage device 116 retrieves the metadata of the corresponding data. The retrieval request of the metadata of the corresponding data may be transmitted to the storage device 116 via a device driver (not shown) for managing the storage device 116. When the device driver receives the retrieval request of the metadata of the data, the device driver controls the storage device 116 to retrieve the metadata of the data stored in the storage device. When the storage device 116 completes the retrieval of the metadata of the corresponding data, the retrieval completion message of the metadata of the corresponding data is transmitted to the file system 113.

The file system 113 transmits the result of the open request of the data (S135).

The application execution unit 110 transmits a read or write command to the data (S140). Since the metadata of the data to be accessed through the open request of the data is stored in the file system 113, the application execution unit 110 transmits a read or write command to the file system 113.

The file system 113 requests the storage device 116 to update the metadata and write or read data (S145). When access to data stored in the storage device 116 occurs to perform writing or reading of data, a change occurs in metadata such as the access time of the log or data of the file system. Therefore, the file system 113 requests the storage device 116 to write or read data, and requests update of the metadata of the data. Since the storage device 116 stores the data and the metadata together, the file system 113 requests the storage device 116 to update the metadata and write or read the data at once.

The storage device 116 writes or reads data, and transmits the execution completion message and the read data to the file system 113 (S150). When the storage device 116 receives a write or read request for data from the file system 113, the storage device 116 writes or reads data stored in the storage device 116, 113). When the storage device 116 receives a read request for data from the file system, the storage device 116 reads the data and transfers the read data to the file system 113 together with the execution completion message.

The file system 113 transmits the result of the data read or write request (S155).

The application execution unit 110 makes a close request for the data. The application execution unit 110 issues a close request notifying the file system 113 that the access to the data has been completed since the application or the data has been read or written to the corresponding data. When the file system 113 receives the close request, the file system 113 deletes the metadata of the stored data.

The application execution unit 110 of the existing data processing apparatus operates in a user mode and the file system 113 and the storage apparatus 116 operate in a kernel mode. Since the application executing unit 110, the file system 113, and the storage device 116 operate in different modes, context switching must be performed in order to make a request to each other. For example, when the application execution unit 110 issues an open request to the file system 113 in S120 of the above-described process, context switching must be performed. In S135, the file system 113 sends the result Context switching must also be performed in the transmission. In a conventional data processing apparatus, both data and meta data are stored in the storage device, and context switching is performed in the process of accessing the metadata in order to read or write data. Accordingly, in the conventional data processing apparatus, even when data is read or written, it is necessary to perform context switching several times. Therefore, an overhead due to context switching may occur. In addition, There is a problem that latency occurs.

An object of the present embodiment is to provide a data processing apparatus and method that improves the data processing speed by using a nonvolatile memory that separately stores meta data of data.

According to an aspect of the present invention, there is provided a data processing apparatus including a file system and a storage device, comprising: a nonvolatile memory for storing meta data of data stored in the storage device separately from the storage device; Volatile memory, a memory capable of directly accessing an address of the non-volatile memory, and an identifier of a file included in a predetermined function to be transmitted to the file system, and acquiring an identifier of a file corresponding to the identifier of the file in the memory And an application executor for confirming the data and including the metadata of the file in the predetermined function and transmitting the metadata to the file system.

According to another aspect of the present invention, there is provided a method of processing a file by a data processing apparatus including a nonvolatile memory, a memory, a file system, and a storage device, the method comprising: Checking metadata corresponding to an identifier of the file in the memory; and if metadata of the file exists, transmitting the metadata of the file to the file system by including the metadata in the predetermined function Wherein the memory directly accesses an address of a nonvolatile memory separately storing meta data of the data stored in the storage device from the storage device to identify whether or not the metadata of the file is present A file processing method, and a file processing method.

As described above, according to an aspect of the present invention, a data processing apparatus and method according to an embodiment of the present invention includes a nonvolatile memory, and changes the structure of a data processing apparatus to separately store meta data of data, It is possible to reduce the number of times of context switching by reducing the number of times of use of the system call, thereby improving the processing speed of the entire data by greatly improving the processing speed for the metadata.

1 is a diagram illustrating a process of an existing data processing apparatus for processing data.
2 is a diagram showing a configuration of a data processing apparatus according to an embodiment of the present invention.
3 is a flowchart illustrating a process for processing data by a data processing apparatus according to an embodiment of the present invention.
4 is a flow chart illustrating a method for an application executor to process data according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference numerals even though they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. Throughout the specification, when an element is referred to as being "comprising" or "comprising", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise . In addition, '... Quot ;, " module ", and " module " refer to a unit that processes at least one function or operation, and may be implemented by hardware or software or a combination of hardware and software.

2 is a diagram showing a configuration of a data processing apparatus according to an embodiment of the present invention.

2, a data processing apparatus 200 according to an embodiment of the present invention includes an application execution unit 210, a file system 220, a storage device 230, a memory 240, and a nonvolatile memory 250 ).

The application execution unit 210 executes an application or software that the user of the data processing apparatus 200 wants to execute. The application executing section 210 has to access data stored in the storage device 230 in order to execute an application or software or the like. That is, the application executing unit 210 accesses the data stored in the storage device 230 via the file system 220 using a predefined function for execution of an application or software.

The file system 220 is a configuration for recording and using data in the storage device 230. The file system 220 controls all operations to record and use data, such as naming, storing, reading, and retrieving data in the storage device 230.

The storage device 230 stores data that can be processed by the data processing apparatus 200. The storage device 230 may be implemented by a hard disk drive (HDD) or a solid state drive (SSD). Unlike the storage device of the existing data processing device, the storage device 230 stores only data that can be processed by the data processing device 200 and stores the meta data of the stored data Do not.

The memory 240 stores temporary data to be stored during execution of the application of the application executing section 210. [ The memory 240 is a high-speed memory for storing temporary data generated in the course of execution of the application executing unit 210, and can be implemented as a cache memory or the like.

In addition, the memory 240 is associated with the non-volatile memory 250 and is directly accessible to the address of the non-volatile memory 250. The memory 240 directly corresponds to the non-volatile memory 250 using a memory mapping or the like. As described above, since the memory 240 directly corresponds to the non-volatile memory 250, the application executing unit 210 can access the memory 240 and access the data stored in the non-volatile memory 250.

Non-volatile memory 250 stores metadata of data stored in storage device 230. The nonvolatile memory 250 stores the metadata of the data stored in the storage device of the existing data processing apparatus together with the data separately from the storage device 230. The nonvolatile memory 250 may be implemented as a non-volatile dual in-line memory module (NVDIMM) in a configuration for storing meta data, but is not limited thereto. For example, Any volatile memory can be substituted.

The data processing apparatus 200 according to an embodiment of the present invention is divided into a user mode 260 and a kernel mode 270. User mode refers to a process execution mode with certain restrictions on access to system memory and CPU instructions, while kernel mode refers to a process execution mode that allows access to all system memory and all CPU instructions. That is, the data processing apparatus 200 gives a higher privilege to the kernel mode than the user mode, thereby preventing an application or the like that may cause malfunctions from harming the safety of the data processing apparatus 200 as a whole.

In order to request a specific system operation from user mode to kernel mode, it should be requested in kernel mode using a predetermined interface. This interface is called a system call. Context switching is performed when the application execution unit 210 executes an application and makes a system call. In the user mode, the execution request of the specific system operation enters the kernel mode after the context switching is performed.

The application executing unit 210 and the memory 240 are operated in the user mode 260 and include the file system 220, the storage device 230, Non-volatile memory 250 operates on kernel mode 270. Accordingly, when the application execution unit 210 requests the file system 220 to perform a specific system operation or when the file system 220 transmits the result or data according to the execution request to the application execution unit 210, . However, context switching does not need to be performed on the application execution unit 210 and the memory 240 located in the same user mode. In view of the relationship between the memory 240 and the nonvolatile memory 250, it seems that context switching is required even for mutual request or transmission / reception of data. However, since the non-volatile memory 250 is mapped to the memory 240 using memory mapping or the like, access between the memory and the non-volatile memory is possible without any context switching.

3 is a flowchart illustrating a process for processing data by a data processing apparatus according to an embodiment of the present invention.

The application execution unit 210 determines the identifier of the file to be processed by the memory 240 (S310). The application execution unit 210 uses a predefined function for execution of an application or software, and identifies an identifier of a file included in a predefined function. For example, a predefined function can use a function such as Write_flash if it wants to process a write command for the file. If you want to process a read command for that file, you can use a function like Read_flash . Also, the predefined function includes an identifier of the file, where the identifier of the file is an argument for identifying each file. The identifier of the file includes an Object Identifier (OID), a unique key value of the file (Unique Key), or a filename of the file (Filename). An OID (Object Identifier) or a unique key value (Unique Key) of an identifier of a file has a value unique to each file, but a file name of a file may have the same file name. Therefore, when the file identifier is a file name of a file, the application execution unit 210 generates a unique value of the file from the file name. For example, the application executing unit 210 may generate a unique value of a corresponding file using a hash function.

The application executing unit 210 checks the metadata of the file corresponding to the identifier of the file in the memory 240 (S320). Metadata is data representing attributes of data such as size of data, storage location, identifier, permission of access, and modified time. Since the memory 240 is mapped to the nonvolatile memory 250 using memory mapping or the like, it is possible to directly access the address of the nonvolatile memory 250 without further context switching. The application execution unit 210 can check the memory 240 without having to access the nonvolatile memory 250 to check the metadata of the file. Accordingly, the application executing unit 210 checks the metadata of the file corresponding to the identifier of the file identified by using the above-described process in the memory 240. [ Since the metadata stored in the nonvolatile memory 250 is sequentially stored with respect to a certain reference such as an ascending order or a descending order, the application executing unit 210 can confirm the metadata of the file corresponding to the identifier of the file . Unlike the conventional data processing apparatus which has to check the metadata through a plurality of context switching processes, the application executing unit 210 can simply check the metadata of the file to be processed from the memory 240.

The application executing unit 210 requests the file system 220 to read or write a corresponding file (S330). The application execution unit 210 requests a read or write command to the file using the function defined in the file system 220. At this time, the read or write command is context switched and transferred to the file system 220. In requesting a read or write command, the application execution unit 210 requests the read or write command by including metadata read from the memory 240 in a read or write command. In particular, the application execution unit 210 may include information on the storage location of data in the metadata by including it in a read or write command. Even if metadata is not stored in the file system through the metadata checking process as in the conventional data processing apparatus, since the metadata is included in the read or write command, no processing is performed on the data read or write command The failure does not occur.

The application execution unit 210 requests the memory 240 to update the metadata (S335). The application execution unit 210 requests the memory 240 to update the metadata because the file to which the read or write command is requested by the application execution unit 210 is to access the data or modify the data.

The memory 240 updates the meta data of the corresponding file when receiving the metadata update request from the application executing unit 210 (S340). Since the memory 240 is associated with the nonvolatile memory 250 as described above, it is possible to easily update the metadata.

The file system 220 requests the storage device 230 to perform reading or writing of the file (S350). The file system 220 requests the storage device 230 to read or write the file, and transmits the metadata of the file together with the file system 220. By transmitting the meta data together, it becomes possible to read or write the corresponding file in the storage device 230. [ The storage device 116 writes or reads data stored in the storage device 116 when receiving a request to read or write the file from the file system 220.

The storage device 230 writes or reads the file, and transmits the completion message and the read data to the file system 220 (S360). The storage device 230 writes or reads a corresponding file stored in the storage device 230, and transmits an execution completion message to the file system 220. Also, when the storage device 230 is requested to read data from the file system 220, the storage device 230 reads the file and transfers the read data to the file system 220 together with the execution completion message.

The file system 220 transmits the result of the file read or write request to the application execution unit 210 (S370).

A conventional data processing apparatus stores metadata in a storage device and stores the metadata in a file system when processing a specific file. Therefore, the application executing unit in the conventional data processing apparatus makes an open request to the file system in order to request the metadata of the specific data according to the read or write command of the specific data. And thus a context switching process occurs. In addition, the system call must be used in the case where the retrieval of the metadata in the storage device in the data processing apparatus is completed and the file system transmits the result of the open request. In addition, a process of removing metadata stored in the file system by performing a close request upon completion of processing according to a read or write command of specific data is required. This process also requires system calls to be used. According to the conventional data processing apparatus, when a specific data read or write command is processed, a process of searching for metadata and notifying of completion of the search, and a process of closing / In the requesting process, the system call must be used and context switching occurs accordingly. However, the data processing apparatus 200 according to an embodiment of the present invention stores and manages meta data in the non-volatile memory 250 rather than the file system 220, and the memory 240 and the non-volatile memory 250 correspond to each other The system call is not used in the process of retrieving the metadata. Even if the processing of the file is completed, a separate close request is unnecessary. Therefore, in order to execute a specific data read or write command in the conventional data processing apparatus, three system calls in total, that is, an open request, a read or write command request and a close request, must be used. On the other hand, The processing unit uses one system call in a read or write execution request. Accordingly, the data processing apparatus according to an embodiment of the present invention can reduce the number of system calls used compared with the conventional data processing apparatus, thereby reducing the context switching process, and thus can have a high processing speed in data processing.

The execution unit 210 of the application of the data processing apparatus may read or write the file at the request of the user of the data processing apparatus. However, there may be a case where merely checking the metadata of the file is necessary. For example, when the application execution unit 210 uses the Stat function (a function for checking metadata information of a specific data) or the readdir function (a function for searching a file or a subdirectory in a directory) Can be performed. In this case, the conventional data processing apparatus should use the system call to receive the result of the open request and the open request as described above, and context switching occurs accordingly. However, the data processing apparatus according to an embodiment of the present invention can confirm the metadata through steps S310 to S330. In S310 to S330 described above, the system call does not need to be used and context switching does not occur. Accordingly, when the data processing apparatus according to an embodiment of the present invention performs only the verification of the metadata, it can have a significantly faster processing speed than the conventional data processing apparatus.

4 is a flow chart illustrating a method for an application executor to process data according to an embodiment of the present invention.

The identifier of the file included in the function to be executed is confirmed (S410). The application execution unit 210 uses a predefined function for execution of an application or software, and identifies an identifier of a file included in a predefined function.

It is checked whether the file identifier is a file name (S420). The identifier of the file is an argument for identifying each file, and includes an OID (Object Identifier), a unique key value of the file (Unique Key), or a file name (Filename) of the file.

If the file identifier is a file name, a unique value is generated from the file name (S430). An OID (Object Identifier) or a unique key value (Unique Key) of an identifier of a file has a value unique to each file, but a file name of a file may have the same file name. Therefore, when the file identifier is a file name, the application execution unit 210 generates a unique value of the file from the file name. For example, the application executing unit 210 may generate a unique value of a corresponding file using a hash function.

The metadata corresponding to the identifier of the file is checked in the memory (S440). If the file identifier is not a filename or a unique value is generated, the metadata corresponding to the identifier of the file is confirmed in the memory. As described above with reference to FIG. 2, since the memory 240 and the non-volatile memory 250 correspond to each other, the application executing unit 210 can easily check the metadata of the file in the memory 240 without context switching.

It is checked whether metadata exists (S450). The application executing unit 210 checks whether metadata corresponding to an identifier of a file exists in the memory.

If metadata of the corresponding file exists, a read or write command including metadata is requested (S460). When the presence of the metadata corresponding to the identifier of the file is confirmed in the memory 240, the application executing unit 210 requests the metadata including the read or write command. In particular, the application execution unit 210 may include information on the storage location of data in the metadata by including it in a read or write command. Even if metadata is not stored in the file system through the metadata checking process as in the conventional data processing apparatus, since the metadata is included in the read or write command, no processing is performed on the data read or write command The failure does not occur.

In FIGS. 3 and 4, it is described that each process is sequentially executed, but this is merely illustrative of the technical idea of an embodiment of the present invention. In other words, those skilled in the art will appreciate that various changes and modifications may be made without departing from the essential characteristics of one embodiment of the present invention, And FIG. 4 are not limited to the time-series order because they can be variously modified and modified by being executed in parallel.

3 and 4 may be embodied as computer-readable codes on a computer-readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. That is, a computer-readable recording medium includes a magnetic storage medium (e.g., ROM, floppy disk, hard disk, etc.), an optical reading medium (e.g., CD ROM, And the like). The computer-readable recording medium may also be distributed over a networked computer system so that computer readable code can be stored and executed in a distributed manner.

The foregoing description is merely illustrative of the technical idea of the present embodiment, and various modifications and changes may be made to those skilled in the art without departing from the essential characteristics of the embodiments. Therefore, the present embodiments are to be construed as illustrative rather than restrictive, and the scope of the technical idea of the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be construed according to the following claims, and all technical ideas within the scope of equivalents thereof should be construed as being included in the scope of the present invention.

110, 210: Application execution unit 113, 220: File system
116 and 230: storage device 200: data processing device
240: memory 250: nonvolatile memory

Claims (8)

A data processing apparatus comprising a file system and a storage device,
A nonvolatile memory for storing meta data of data stored in the storage device separately from the storage device;
A memory corresponding to the nonvolatile memory and directly accessible to an address of the nonvolatile memory; And
Determining an identifier of a file included in a predetermined function to be transmitted to the file system, checking metadata of a file corresponding to the identifier of the file in the memory, and storing metadata of the file in the predetermined function, An application execution unit
The data processing apparatus comprising: The method according to claim 1,
The memory comprising:
Volatile memory through a memory mapping process. ≪ Desc / Clms Page number 19 > The method according to claim 1,
The identifier of the file is,
A file name, a unique key value, or an OID (Object Identifier). The method of claim 3,
The application execution unit,
And generates an eigenvalue of the file from the file name if the identifier of the file is the file name. 5. The method of claim 4,
The application execution unit,
Wherein a hash function is used to generate the eigenvalue of the file from the file name. The method according to claim 1,
The application execution unit,
Transmits the predetermined function to the file system, and requests the memory to update the metadata transmitted from the memory. The method according to claim 1,
The application execution unit,
Wherein the predetermined function includes information on which of the storage devices the file is stored, and transmits the file to the file system. CLAIMS What is claimed is: 1. A method for processing a file by a data processing apparatus comprising a non-volatile memory, a memory, a file system and a storage device,
Determining an identifier of a file included in a predetermined function to be transmitted to the file system;
Checking metadata corresponding to an identifier of the file in the memory;
If the metadata of the file exists, including metadata of the file in the predetermined function and transmitting the meta data to the file system,
Wherein the memory directly accesses an address of a nonvolatile memory separately storing meta data of the data stored in the storage device to identify the presence or absence of metadata of the file. Processing method.

Images