KR20120045422A - Memory system and user device, and data management method thereof - Google Patents

Abstract

PURPOSE: A memory system and a user device, and a data management method thereof are provided to eliminate a mismatch between a file management unit of a hard disk and a data management unit of a flash memory, thereby preventing lifetime reduction of the flash memory. CONSTITUTION: A file system manages a file by a unit different from a data management unit of a data storage device and changes information about metadata of a file to be deleted. A trim management module(113) provides information about a storage area to the data storage device wherein the storage area is matched with a data management unit of the data storage device. A change of information about the metadata of the file to be deleted is deleted at an upper level.

Description

MEMORY SYSTEM AND USER DEVICE, AND DATA MANAGEMENT METHOD THEREOF

The present invention relates to a memory system and a data management method thereof, and more particularly to a flash memory system and a data management method thereof.

Since flash memory does not support overwriting unlike a hard disk, an erase operation must be preceded to write again. The erase operation of the flash memory is performed in units of memory blocks. Due to the characteristics of the flash memory, it is difficult to apply the file system for the hard disk to the flash memory as it is. To solve this problem, a middleware flash translation layer (FTL) is used between the hard disk file system and the flash memory. The flash translation layer allows flash memory to be freely read and written like traditional hard disks.

On the other hand, a unit for managing a file in a file system and a unit for managing data stored in a flash memory in a flash translation layer are different. Such inconsistency in the management unit can cause unnecessary copying operation and large amount of merging operation in the flash memory. This copy and merge operation is a major cause of shortening the life of flash memory.

An object of the present invention is to eliminate the inconsistency between the management unit from the hard disk perspective and the management unit from the flash memory perspective, thereby preventing shortening the life of the flash memory and improving the overall performance of the flash memory system.

According to an embodiment of the present invention, a data storage method of a user device which stores data of a file in a data storage device and has a data management unit different from that of the data storage device, may respond to a file deletion request, and transmit metadata of the file requested to be deleted. Changing; Determining whether information about a storage area of the file requested to be deleted corresponds to a data management unit of the data storage device; And transmitting information on an area corresponding to a data management unit of the data storage device, to the data storage device, from among information on a storage area of the file requested to be deleted.

In an embodiment, the change of the metadata of the file requested to be deleted indicates that the file to be deleted is deleted at a higher level.

The method may further include generating a trim management table that manages information about an area that does not match a data management unit of the data storage device among information about a storage area of the file requested to be deleted.

In an embodiment, information about a storage area of the file requested to be deleted is provided from a mapping table of the data storage device.

A user device for storing data of a file in a data storage device according to an embodiment of the present invention manages the file in a unit different from that of the data management unit of the data storage device, and changes information on metadata of the file requested to be deleted. File system; And a trim management module configured to provide the data storage device with information about a storage area corresponding to a data management unit of the data storage device among information about a storage area of the file requested to be deleted.

In an embodiment, the change of the information about the metadata of the file requested to be deleted indicates that the file to be deleted is deleted at a higher level.

The trim management table may further include a trim management table that manages information about an area that does not match a data management unit of the data storage device among information about a storage area of the file requested to be deleted.

In an embodiment, the apparatus further includes a host memory that stores the trim management table, and the trim management table stored in the host memory is managed by a push method.

In an embodiment, the apparatus may further include a host memory configured to store information regarding a storage area of at least two files requested to be deleted.

In example embodiments, the trim management module may be configured to transmit, to the data storage device, information on an area corresponding to a data management unit of the data storage device among information on a storage area of the at least two files requested to be deleted stored in the host memory. to provide.

In an embodiment, information about a storage area of the file requested to be deleted is provided from a mapping table of the data storage device.

In an embodiment, a memory system may include a host supporting a trim operation; And a data storage device that performs an erase operation in response to a trim command from the host, wherein the host corresponds to a storage area that matches a data management unit of the data storage device among information about a storage area of a file requested to be deleted. Only information relating to the data storage device is provided.

In an embodiment, the host separately manages information about an area that does not match a data management unit of the data storage device among information about a storage area of the file requested to be deleted.

In an embodiment, the host manages a file on a sector basis, the data storage device manages data of a file on a page basis, and each page is divided into a plurality of sectors.

According to an embodiment of the present disclosure, the host may manage a file on a sector basis and change the information on metadata of a file requested to be deleted; And a trim management module for selecting information on sectors corresponding to a page unit which is a data management unit of the data storage device, among sectors of the file to be deleted.

In an embodiment, the change of the information about the metadata of the file requested to be deleted indicates that the file to be deleted is deleted at a higher level.

In example embodiments, the host further includes a trim management table that manages information on sectors (hereinafter, partial sectors) that do not match the page unit among sectors of the file requested to be deleted.

In an embodiment, the trim management table manages information about the partial sector and information about a sector belonging to the same page as the partial sector.

In an embodiment, the host further includes a host memory that stores information about sectors of at least two files requested to be deleted at different times.

In example embodiments, the trim management module may select information on a sector address corresponding to a management unit of the data storage device from among information about sectors of at least two files requested to be deleted at different times stored in the host memory. do.

The memory system according to an exemplary embodiment of the present invention eliminates inconsistencies between a file management unit in a hard disk view and a data management unit in a flash memory view, thereby eliminating the copying and bulk merging operations of valid data caused by the inconsistency of the data management unit. Prevent occurrence. Therefore, the memory system according to the embodiment of the present invention prevents shortening the life of the flash memory and improves the overall performance of the flash memory system. In addition, the memory system according to an embodiment of the present invention further supports a trim operation, thereby further improving a response speed of the flash memory system to a command of a host.

1 is a block diagram illustrating a memory system according to an example embodiment of the disclosure.
2 is a block diagram illustrating a flash memory system according to an exemplary embodiment of the present invention.
FIG. 3 exemplarily illustrates a directory entry structure generated by the file system of FIG. 2 to manage files.
4 is a block diagram illustrating a software hierarchy structure of the flash memory system illustrated in FIG. 2.
5 is a block diagram illustrating the operation of the trim management module of FIG. 2 in more detail.
6 is a block diagram illustrating an address translation operation of the flash translation layer of FIG. 2 in more detail.
7 is a block diagram illustrating an example of address translation through a mapping table.
FIG. 8 is a diagram illustrating an embodiment of a flash memory system that processes a trim command when there is no trim management module of FIG. 2.
9 to 11 are flash memories according to an embodiment of the present invention for generating an aligned sector address (Aligned Sector ADDR) using the trim management module of FIG. 2 and processing a trim command including the aligned sector address. It is a figure for demonstrating a system.
12 is a flowchart illustrating group information being transferred from a mapping table of a flash storage device to a host.
FIG. 13 is a flowchart illustrating an operation of the trim management module of FIG. 2.
14 is a diagram illustrating a host that collects information about sector addresses provided at different times and processes information about the collected sector addresses.
FIG. 15 is a flowchart illustrating an operation in which sector addresses for different files are collected in the sector storage area of FIG. 14.
FIG. 16 is a flowchart illustrating an operation of processing sector addresses collected in the sector collection area of FIG. 14 at idle time.
17 shows an example in which a host is applied to a memory card according to an embodiment of the present invention.
18 illustrates an embodiment in which a host is applied to a solid state drive (SSD) according to an embodiment of the present invention.
FIG. 19 is a block diagram illustrating a configuration of an SSD controller shown in FIG. 18.
20 is a block diagram illustrating an example in which a host is implemented in a flash memory module according to an example embodiment.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments or application examples of the present invention will be described with reference to the accompanying drawings so that those skilled in the art may easily implement the technical idea of the present invention. Shall be.

Ⅰ. Hosts that Support Trim Motion

1 is a block diagram illustrating a memory system 100 according to an exemplary embodiment of the inventive concept. Referring to FIG. 1, the memory system 100 includes a host 110 and a storage device 120, and the storage device 120 includes a control unit 121 and a storage unit 122.

The host 110 includes a processing unit 111 and a drive unit 112. The processing unit 111 controls the overall operation of the host 110, and the driving unit 112 drives the storage device 120 under the control of the processing unit 111.

The host 100 supports a trim operation. The trim operation means that when there is a delete request for a specific file from the user, the host 110 processes only metadata about the file. In this case, since only the meta data of the host 110 is processed without the substantial deletion of the data stored in the storage unit 122, the user can recognize that the deletion operation on the file is performed quickly.

In order to substantially delete the data stored in the storage unit 122, the host 110 provides a trim command to the storage device 120. The trim command contains information (eg, address information) for specifying the area to be substantially deleted. The control unit 121 performs an erase operation on the data stored in the storage unit 122 in response to the trim command. The trim command may be defined by various names such as a deallocate command, an unwrite command, a deletion command, a file delete command, and the like.

Meanwhile, a unit for managing a file in the host 110 and a unit for managing data stored in the storage unit 122 in the storage device 120 may be different from each other. For example, the host 110 manages files in sector units in terms of a hard disk, and the storage device 120 stores pages and / or blocks in terms of a flash memory. Data stored in the storage unit 122 may be managed in units of blocks.

Such inconsistency between the management unit of the host 110 and the storage device 120 may cause performance degradation of the memory system 100. For example, if an erase operation is performed on the data stored in the storage unit 122 in response to a trim command from the host 110, the discrepancy of the management unit may be a copy operation of the data and a large merge operation. may cause a merge operation. Therefore, the lifespan of the storage device 120 may be shortened and performance may be degraded.

In order to solve this problem, the host 110 according to an embodiment of the present invention includes a trim management module 113. When the trim command is provided to the storage device 120, the trim management module 113 manages a management unit of the storage device 120 (eg, a sector address) to designate an area to be deleted. Only information corresponding to the page unit) is provided to the storage device 120. By resolving a mismatch between management units between the host 110 and the storage device 120 using the trim management module 113, the memory system 100 according to the embodiment of the present invention shortens the lifespan of the storage device 120. And deterioration in performance.

II. Hosts of flash memory systems to resolve inconsistencies in management units

2 is a block diagram illustrating a flash memory system 1000 according to an example embodiment. In FIG. 2, the flash storage device 1200 is illustrated as an example of the storage device 120 of FIG. 1.

Referring to FIG. 2, the flash memory system 1000 includes a host 1100 and a flash storage device 1200. For simplicity, the host 1100 manages a file in sectors, and the flash storage device 1200 manages data stored in the flash memory 1210 in units of pages. Is assumed.

The host 1100 according to the embodiment of the present invention includes a trim management module 1124. The host 1100 uses the trim management module 1123 to resolve inconsistencies in the management unit between the host 1100 and the flash storage device 1200. Referring to FIG. 2, the host 1100 includes a processing unit 1110 and a driving unit 1120.

The processing unit (eg, CPU) 1110 controls the overall operation of the host 1100, and the driving unit 1120 drives the flash storage device 1200 under the control of the processing unit 1110. The driving unit 1120 may include a memory for driving software programs of the host 1100.

The driving unit 1120 includes an application 1121, a file system 1122, a device driver 1123, a trim management module 1124, and a host memory 1125. The application 1121 is also called an application program, and is software running on an operating system (OS). For example, application 1121 is programmed to support the creation and deletion of files.

File system 1122 manages files used by host 1100. The file system may manage files on a sector or cluster basis from a hard disk perspective. In the following description, it is assumed that the file system 1122 manages a file used in the host 1100 on a sector basis from a hard disk perspective. Here, the sector is the smallest data management unit that can be accessed by the application 1121, and generally has a size of 512B (byte).

The file system 1122 changes the metadata of the file requested to be deleted when there is a request to delete a specific file from the application 1121. Thereafter, when the application 1121 accesses the file, the file system 1122 refers to the changed metadata and provides information that the file has been deleted. File system 1122 also forwards sector address for the file requested to be deleted to trim management module 1124. The file system 1122 and directory entry structure of the file system 1122 are described in more detail in FIG. 3 below.

The trim management module 1124 receives a sector address for the file requested to be deleted from the file system 1122. The trim management module 1124 matches the received sector address to the page unit of the flash memory. That is, the trim management module 1124 selects only sector addresses corresponding to the page unit of the flash storage device 1200 among the received sector addresses. In order to substantially delete data stored in the flash memory 1210, the trim management module 1124 provides a sector address corresponding to a page unit to the flash storage device 1200 along with a trim command. The trim management module 1124 may separately manage sector addresses that do not correspond to the page unit of the flash storage device 1200 among the received sector addresses.

The device driver 1123 is a program that enables the flash storage device 1200 to communicate with the host 1100. In order to use the flash storage device 1200, a device driver 1123 corresponding to the flash storage device 1200 must be installed in the host 1100. In FIG. 2, the trim management module 1124 and the device driver 1123 are implemented as modules independent of each other. However, this is exemplary and the trim management module 1124 may be mounted in the device driver 1123.

The host memory 1125 may temporarily store data written to or read from the flash storage device 1200. In addition, the host memory 1125 may be used as a working memory for driving the application 1121, the file system 1122, the device driver 1123, and the trim management module 1124.

Meanwhile, the flash storage device 1200 receives a trim command from the host 1100. The trim command includes information for specifying an area to be erased (for example, information about a sector address requested to be erased). In this case, the information for designating the area to be deleted provided to the flash storage device 1200 may be stored by the trim management module 1124 of the host 1100 in a management unit (eg, page unit) of the flash storage device 1200. Will match.

In response to the trim command, the flash storage device 1200 marks an area of the flash memory 1210 that is requested to be deleted as invalid. The flash storage device 1200 performs an erase operation on an area marked as invalid at an idle time (for example, an idle time of the control unit 1230 when there is no request from the host). do. 2, the flash storage device 1200 may include a flash memory 1210, a buffer memory 1220, and a control unit 1230.

The flash memory 1210 performs an erase operation, a read operation, or a write operation under the control of the control unit 1230. The flash memory 1210 is composed of a plurality of memory blocks. Each memory block is composed of a plurality of pages. In FIG. 2, three memory blocks 1211 to 1213 are illustrated. Each memory block is illustratively shown as having four pages.

The size of each page is larger than the size of a sector. For example, each page has a size of about 2KB (byte) and a sector has a size of 512B (byte). The flash memory 1210 performs an erase operation in units of memory blocks, and performs a write or read operation in units of pages.

Meanwhile, one bit or two or more bits of data may be stored in one memory cell of the flash memory 1210. A memory cell capable of storing one bit data in one memory cell is called a single level cell (SLC) or a single bit cell. A memory cell capable of storing two or more bits of data in one memory cell is called a multi level cell (MLC) or a multi bit cell.

The buffer memory 1220 may temporarily store data read from the flash memory 1210 or data provided from the host 1100. In addition, the buffer memory 1220 may be used to drive firmware, such as a Flash Transslation Layer (FTL). The buffer memory 1220 may be implemented with DRAM, SRAM, MRAM, PRAM, and the like.

The control unit 1230 includes a central processing unit (CPU) 1231, a flash translation layer (FTL) 1232, a flash controller 1233, and a buffer controller 1234. The CPU 1231 analyzes and processes a signal input from the host 1100. Also, the CPU 1231 controls the overall operation of the flash storage device 1200.

The flash translation layer 1232 converts a logical address (LA) provided from the host 1100 into a physical address (PA) on the flash memory 1210. For example, the flash translation layer 1232 converts a sector address received from the host into a page address on the flash memory 1210.

In addition, the flash translation layer 1232 manages data stored in the flash memory 1210 in units of pages, for example. The flash translation layer 1232 marks the page as invalid when all data stored in a predetermined page is requested to be deleted by a trim command from the host 1100.

The flash controller 1233 controls read, write and erase operations of the flash memory 1210. For example, at idle time of the control unit 1230, the flash controller 1233 controls the flash memory 1210 to perform an erase operation on an invalidally marked page. The buffer controller 1234 controls read and write operations of the buffer memory 1220.

3 exemplarily illustrates a directory entry structure that the file system 1122 of FIG. 2 generates to manage files. Referring to FIG. 3, a directory entry structure includes a file name, an extension, an attribute, a create date and time, a starting secter, and a file size information ( file size).

The file system 1122 (see FIG. 2) changes the metadata of the file requested to be deleted when there is a deletion request for a specific file from the application 1121 (see FIG. 2). For example, the file system 1122 places the hexadecimal byte code 'E5h' in the file name of the file requested to be deleted. As another example, the file system 1122 changes the attribute value of the file requested to be deleted to 'OxE5'. This is one special tag, which means that this file has been deleted. Thus, when application 1121 subsequently accesses the file, file system 1122 provides information that the file has already been deleted. Information about file system 1122 may be stored in nonvolatile memory (eg, flash memory 1210) periodically or using idle time.

The file system 1122 may be variously selected according to an operating system (OS) of the flash memory system 1000 (refer to FIG. 2). For example, if the operating system of the flash memory system 1000 is a disk operating system (DOS) or a Windows-based operating system, a file allocation table (FAT) file system, a virtual FAT (VFAT) File systems such as file systems, extended FAT (exFAT) file systems, new technology file systems (NTFS), and the like may be used.

As another example, when the operating system of the flash memory device 1000 is a unit-based operating system, a UNIX file system (UFS) may be used. If the operating system of the flash memory device 1000 is a Linux-based operating system, a file system for LINUX may be used. When the operating system of the flash memory device 1000 is a mobile OS (eg, iOS (OS for iPhone, iPad) and Android OS), the file system for the mobile OS may be used.

4 is a block diagram illustrating a software hierarchy of the flash memory system 1000 illustrated in FIG. 2. Referring to FIG. 4, the software hierarchy of the flash memory system 1000 includes an application 1121, a file system 1122, a trim management module 1124, a flash translation layer 1232, and a flash memory 1210. do. The application 1121, the file system 1122, and the trim management module 1124 on the host 1100 (see FIG. 2) may be referred to as a high level. The flash translation layer 1232 and the flash memory 1210 on the side of the flash storage device 1200 (refer to FIG. 2) may be referred to as a low level.

Application 1121 communicates a file delete request to file system 1122. In response to the file deletion request, file system 1122 changes the metadata of the file requested to be deleted. For example, file system 1122 places 'E5h' in the file name (see FIG. 3). Thus, if the application 1121 subsequently accesses the file, the file system 1122 may provide information that the file has been deleted. The file deletion request of the application 1121 and thus the metadata of the file system 1122 may be referred to as a 'delete operation at a high level'.

The trim management module 1124 receives a sector address (Sector ADDR) for the file requested to be deleted from the file system 1122. The trim management module 1124 selects a sector address corresponding to the page unit of the flash memory 1210 among the received sector addresses Sector ADDR. The sector address matched to the page unit of the flash memory 1210 may be referred to as an aligned sector address (Aligned Sector ADDR).

In addition, the trim management module 1124 may separately manage sector addresses that do not correspond to the page unit of the flash storage device 1200 (refer to FIG. 2) among the sector addresses received using the trim management table. .

Meanwhile, in order to substantially delete data stored in the flash memory 1210, the trim management module 1124 provides a trim command TRIM cmd to the flash translation layer 1232. The trim command includes an aligned sector address (Aligned Sector ADDR) for specifying a file requested to be deleted. The flash translation layer 1232 converts the aligned sector address (Aligned Sector ADDR) to a page address (Page ADDR), and marks the page of the flash memory 1210 to be deleted as invalid. do.

The flash memory 1210 performs an erase operation on a page marked as invalid, for example, at idle time. For example, the idle time means a time when there is no request from the host 1100 (see FIG. 2) to the control unit 1230 (see FIG. 2). As is well known, since the flash memory 1210 performs an erase operation on a block basis, an erase operation on a page of the flash memory 1210 may be performed by copying and merging data and block erasing operation. erase operation). The marking operation of the flash translation layer 1232 and the erasing operation of the flash memory 1210 may be referred to as an erase operation at a low level.

5 is a block diagram illustrating the operation of the trim management module 1124 of FIG. 2 in more detail. Referring to FIG. 5, the trim management module 1124 receives a sector address (Sector ADDR) and outputs a sector address (that is, an aligned sector address (Aligned Sector ADDR)) corresponding to a page unit. The information about the sector address (Sector ADDR) and the aligned sector address (Aligned Sector ADDR) may include a start sector number (Start Sector No) and the number of sectors (# of Sectors), respectively.

In detail, the trim management module 1124 selects a sector address (i.e., an aligned sector address (Aligned Sector ADDR)) corresponding to the page unit among the sector addresses (Sector ADDR) with reference to the group information. Herein, the group information means address information of sectors corresponding to one page, and the trim management module 1124 may receive group information from, for example, a mapping table of the flash translation layer 1232. The group information and the mapping table are described in more detail in FIG. 9 below.

In addition, the trim management module 1124 may separately manage a sector address that does not match a page unit among the received sector addresses (Sector ADDR). For this purpose, the trim management module 1124 may include a trim management table.

Meanwhile, information about the trim management table may be stored in the host memory 1125 (see FIG. 2). In this case, the size of the area allocated to the trim management table among the areas of the host memory 1125 may be variously set by the designer. For example, in order to reduce the overhead of the processing unit 1110 according to sector address management (see FIG. 2), the size of the area allocated to the trim management table may be limited to a predetermined size.

When the area allocated to the trim management table is limited to a predetermined size, the size of information about the sector address to be managed in the trim management table may exceed the area allocated to the host memory 1125. In this case, the information about the sector address of the trim management table can be managed by the pushing method. The operation of the trim management module 1124 and the trim management module 1124 is described in more detail below with reference to FIGS. 9 through 11.

6 is a block diagram illustrating the address translation operation of the flash translation layer 1232 of FIG. 2 in more detail. Referring to FIG. 6, the flash translation layer 1232 converts an aligned sector address (Aligned Sector ADDR), which is a logical address, into a page address (Page ADDR), which is a physical address on the flash memory 1210. To convert.

Address translation of the flash translation layer 1232 may be performed through a mapping table. There are two types of mapping methods: page mapping and block mapping. Page mapping performs address translation in units of pages (eg, 2 KB), and block mapping scheme performs address translation in units of blocks (eg, 1 MB). Address translation through the mapping table is described in more detail in FIG. 7 below.

The address translation of the flash translation layer 1232 is performed by a read operation, a write operation, and an erase operation performed by the actual flash memory 1210 when viewed in a high level application 1121 or a file system 1122. It looks like a hard disk device's read or erase operation. That is, the flash translation layer 1232 performs an emulate function.

7 is a block diagram illustrating an example of address translation through a mapping table. For simplicity, hereinafter, it is assumed that address translation through page mapping is performed.

Referring to FIG. 7, a mapping table maps a sector address (Sector ADDR), which is a logical address, to a page address (Page ADDR), which is a physical address. For convenience of explanation, it is assumed that four sectors are mapped to one page. For example, as illustrated in FIG. 7, first to fourth sectors Sector1 to Sector4 may be mapped to the third page Page3.

The mapping table indicates whether the data stored in the page is valid data through the write state information (WSI). For example, the 'v' indication of the write status information WSI indicates that the data stored in the page is valid data.

The pages Page0 to Page3 of the memory block 1211 of the flash memory 1210 are assumed to be divided into four subpages Sub_Page0 to Sub_Page3, respectively. The size of each subpage is equal to each sector, and each subpage is assumed to correspond to each sector. For example, as illustrated in FIG. 7, the third page Page3 is divided into four subpages Sub_Page0 to Sub_Page3, and four subpages Sub_Page0 to Sub_Page4 of the third page Page3. Are assumed to correspond to the first to fourth sectors Sector1 to Sector4, respectively.

Meanwhile, for convenience of description, in FIGS. 8 to 11, three files File1 to File3 are valid data, and the first to third pages Page1 to 3 of the block 1211 are valid data. It is assumed to be stored in In this case, the first file File1 corresponds to the first to fifth sectors Sector1 to Sector5, and the second file File2 corresponds to the sixth to eighth sectors Sector6 to Sector8. It is assumed that the third file File3 corresponds to the ninth to twelfth sectors Sector9 to Sector12.

FIG. 8 is a diagram illustrating an embodiment of a flash memory system 1000 that processes a trim command when the trim management module 1124 of FIG. 2 does not exist. That is, FIG. 8 illustrates an example in which a sector address that does not correspond to a page unit is provided to the flash storage device 1200. For the sake of brevity, it is assumed that a trim command TRIM cmd is provided that includes information about the sector address of the first file File1.

Referring to FIG. 8, a trim command TRIM cmd is provided from the host 1100. The trim command TRIM cmd includes a sector address for designating an area to be erased in the flash memory 1210. As shown in FIG. 8, information about a sector address may be provided as a start sector number (Start Sector No) and the number of sectors (# of Sectors). For example, since the first file File1 corresponds to the first to fifth sectors Sector1 to Sector5, the starting sector number may be '1' and the number of sectors may be '5'.

When the trim command TRIM cmd is provided from the host 1100, the flash translation layer 1232 (see FIG. 2) updates the write state information WSI of the mapping table. That is, the write status information WSI of the page corresponding to the received sector address is marked as invalid. For example, the 'x' indication of the write state information WSI illustrated in FIG. 8 means that the data stored in the corresponding page is invalid data.

In detail, the first file File1 corresponds to the first to fifth sectors Sector1 to Sector5. In this case, the first to fourth sectors Sector1 to Sector4 of the first file File1 correspond to the third page Page3. Therefore, the write status information WSI for the third page Page3 of the mapping table is marked as invalid. The fifth sector Sector5 of the first file File1 corresponds to the second page Page2. Therefore, the write status information WSI of the third page Page3 is marked as invalid. Erase opeation for the invalidally marked second and third pages Page2, Page3 is performed, for example, at an idle time of the control unit 1230 (see FIG. 2).

Meanwhile, data corresponding to the fifth sector Sector5 of the first file File1 is stored in the subpage 0 of the second page Page2, and the subpages 1 to 2 of the second page Page2 are stored. 3) data corresponding to sixth to eighth sectors Sector6 to Sector8 of the second file File2 is stored.

Therefore, when the second page Page2 is marked as invalid by the trim command TRIM cmd for the first file File1, valid data of the second file File2 may be deleted together. Therefore, in order to prevent the valid data of the second file File2 from being deleted, the flash memory 1210 stores data stored in the subpages 1 to 3 of the second page Page2 in another page (eg, Copy to another block 1212 (see FIG. 2).

Such a copy operation may shorten the life of the flash memory 1210 due to an increase in the number of writes. In addition, a new page for storing valid data generated through the copy operation may cause an increase in the merging operation for generating a free block.

In order to solve this problem, the host 1100 according to an embodiment of the present invention includes a trim management module 1124 (see FIG. 2). Since the trim management module 1124 provides the flash storage device 1200 with a sector address corresponding to the management unit of the flash storage device 1200, the copy operation does not occur. This is described in more detail with reference to FIGS. 9 to 11 below.

9 through 11 illustrate an embodiment of generating an aligned sector address (Aligned Sector ADDR) using the trim management module 1124 of FIG. 2 and processing a trim command including the aligned sector address. A diagram for describing the flash memory system 1000 is described.

In an embodiment of the present disclosure, the host 1100 provides an aligned sector ADDR to the flash storage device 1200. To this end, the host 1100 requests group information from the flash storage device 1200. The flash storage device 1200 obtains group information from the mapping table and provides it to the host 1100. Subsequently, when there is a deletion request for a predetermined file, the trim management module 1124 of the host 1100 determines whether the received sector address corresponds to a page unit by referring to the group information. The trim management module 1124 provides a sector address corresponding to a page unit to the flash storage device 1200 with a trim command.

In detail, FIG. 9 illustrates a process in which group information is transmitted from the mapping table of the flash storage device 1200 to the host 1100. Referring to FIG. 9, first, the host 1100 requests group information from the flash storage device 1200. For example, the trim management module 1124 or the processing unit 1110 (see FIG. 2) of the host 1100 may request group information from the flash storage device 1200 at power up.

The flash storage device 1200 provides group information to the host 1100 in response to the group information request from the host 1100. Here, the group information means address information of sectors corresponding to one page. The flash storage device 1200 may obtain group information from, for example, a mapping table.

For example, referring to the mapping table, four sectors correspond to one page. That is, the first to fourth sectors Sector1 to Sector4 correspond to the third page Page3, and the fifth to eighth sectors Sector5 to Sector8 correspond to the second page Page2, and the ninth The twelfth sectors Sector9 to Sector12 correspond to the first page Page1.

Accordingly, the flash storage device 1200 may include first to fourth sectors, fifth to eighth sectors, and ninth to twelfth sectors in one group, and each group of sectors may be divided into one page. Information corresponding (ie, group information) is provided to the host 1100. The group information transferred to the host 1100 may be stored in, for example, the host memory 1125 (see FIG. 2).

10 and 11 illustrate operations of the trim management module 1124 and the flash translation layer 1232 in the case where there is a deletion request for a predetermined file. Referring to FIG. 10, it is assumed that the trim management module 1124 receives a sector address (Sector ADDR) for the first file. That is, it is assumed that the sector address (Sector ADDR) of the first file File1 is provided from the file system 1122 (see FIG. 2) after the deletion operation at the upper level with respect to the first file File1 is performed.

The trim management module 1124 receives a sector address (Sector ADDR) for the first file File1 from the file system 1122. Since the first file File1 corresponds to the first to fifth sectors Sector1 to Sector5, the start sector number (Start Sector No) is '1' and the number of sectors (# of Sectors) may be '5'. have. The trim management module 1124 refers to the group information stored in the host memory 1125 and determines whether the received sector address corresponds to a page unit.

Specifically, referring to the group information of FIG. 9, the first to fourth sectors Sector1 to Sector4 constitute one group. That is, the first to fourth sectors Sector1 to Sector4 correspond to a page unit that is a management unit of the flash storage device 1200. On the other hand, the fifth sector Sector5 does not correspond to the page unit.

In this case, the trim management module 1124 generates a trim management table for managing the fifth sector Sector5 that does not correspond to the page unit. The trim management table includes group information and write status information WSI for the fifth sector Sector5, for example, as shown in FIG. Since the data corresponding to the fifth sector Sector5 is deleted at a higher level, the trim management module 1124 marks the write status information WSI for the fifth sector Sector5 of the trim management table as invalid. .

Meanwhile, the first to fourth sectors Sector1 to Sector4 correspond to page units. Accordingly, the trim management module 1124 may generate a sector address (ie, start sector number '1', number of sectors '4') for the first to fourth sectors Sector1 to Sector4 and the trim command TRIM cmd. Together with the flash storage device 1200.

Since the first to fourth sectors Sector1 to Sector4 are mapped to the third page Page3, the flash translation layer 1232 invalidates the write state information WSI for the third page Page3 of the mapping table. Mark it as An erase operation on the invalidally marked third page Page3 is performed at an idle time of the control unit 1230 (see FIG. 2), for example. In this case, since all data stored in the third page Page3 to be erased are invalid data, the copy operation as shown in FIG. 8 is not performed.

On the other hand, according to the deletion request for another file generated later, all of the write status information (WSI) of the group managed in the trim management table can be updated to invalid. In this case, since the sectors of the group correspond to the page unit, the trim management module 1124 may provide sector addresses for the sectors to the flash storage device. This is described in more detail in FIG. 11 below.

Referring to FIG. 11, it is assumed that the trim management module 1124 is provided with a sector address (Sector ADDR) for the second file File2. That is, it is assumed that the sector address of the second file File2 is provided from the file system 1122 after the deletion operation at the upper level with respect to the second file File2 is performed.

The trim management module 1124 receives a sector address (Sector ADDR) for the second file File2 from the file system 1122. Since the second file File2 corresponds to the sixth to eighth sectors Sector6 to Sector8, the starting sector number may be '6' and the number of the colorants may be '3'. The trim management module 1124 refers to the group information stored in the host memory 1125 and determines whether the received sector address corresponds to a page unit.

Specifically, referring to the group information of FIG. 9, the sixth to eighth sectors Sector6 to Sector8 do not correspond to a page unit. Accordingly, the trim management module 1124 separately manages the sixth to eighth sectors Sector6 to Sector8 using the trim management table. In this case, the trim management table for the fifth to eighth sectors Sector5 to Sector8 is already generated by the deletion request for the first file File1. Accordingly, the trim management module 1124 updates the write state information WSI for the sixth to eighth sectors Sector6 to Sector8 as invalid as shown in FIG. 11.

In this case, all of the write state information WSI for the fifth to eighth sectors Sector5 to Sector8 belonging to the same group are invalid. That is, the fifth to eighth sectors Sector5 to Sector8 correspond to page units and correspond to files deleted at a higher level. Accordingly, the trim management module 1124 may generate a sector address (ie, start sector number '5', number of sectors '4') for the fifth to eighth sectors Sector5 to Sector8 and the trim command TRIM cmd. Together with the flash storage device 1200. In this case, the information about the fifth to eighth sectors Sector5 to Sector8 will be deleted from the trim management table.

Meanwhile, since the fifth to eighth sectors Sector5 to Sector8 are mapped to the second page Page2, the flash translation layer 1232 may write write state information WSI for the second page Page2 of the mapping table. Mark as invalid. An erase operation for the invalidally marked second page Page2 is performed, for example, at an idle time of the control unit 1230 (see FIG. 2). Therefore, the erase operation for the second page Page2 will be performed at a later idle time (eg, the idle time of the control unit 1230 (see FIG. 2)).

As described above, the trim management module 1124 of the host 1100 provides only the sector address corresponding to the page unit among the sector addresses received from the file system 1122 to the flash storage device 1200. Therefore, the flash storage device 1200 does not perform an unnecessary copy operation as shown in FIG. 8. This means that the merging operation caused by the unnecessary copying operation can be prevented. That is, by eliminating the mismatch between management units between the host 1110 and the flash storage device 1120 using the trim management module 1124 of the host 1100, the lifespan and performance degradation of the flash storage device 120 are prevented. Can be.

On the other hand, the size of the memory allocated to the trim management table (for example, the host memory 1125 (see Fig. 2)) may be limited to a predetermined size, in this case, the size of information on the sector address to be managed in the trim management table May exceed the size allocated to host memory 1125.

When the size of the information about the sector address to be managed in the trim management table exceeds the size allocated to the host memory 1125, the information about the sector managed in the trim management table may be deleted by an extrusion method. That is, the information about the oldest sector among the information about the sector managed by the trim management table may be deleted, and the information about the newly requested sector may be managed.

For example, it is assumed that information about a first sector, a fifth sector, and a ninth sector belonging to different groups is managed in the trim management table. In addition, when information about the thirteenth sector Sector 13 belonging to another group must be managed in the trim management table, and when information about the thirteenth sector is managed, the sector address to be managed in the trim management table is managed. It is assumed that the size of the information exceeds the size of the area allocated to the trim management table. In this case, the trim management module 1124 may delete information on the oldest first sector Sector1 from the trim management table and manage information on the thirteenth sector Sector13 in the trim management table.

FIG. 12 is a flowchart illustrating that group information is transferred from the mapping table of the flash storage device 1200 to the host 1100.

In operation S110, the host 1100 requests group information from the flash storage device 1200. For example, the host 1100 may request the group storage information from the flash storage device 1200 upon power up. The flash storage device 1200 may obtain group information for each sector from the mapping table in response to the request of the host 1100.

In step S120, the group information is stored in the host memory 1125 of the host 1100. That is, the flash storage device 1200 provides the group information obtained from the mapping table to the host 1100, and the host 1100 stores the transferred group information in the host memory 1125.

FIG. 13 is a flowchart illustrating an operation of the trim management module 1124 of FIG. 2.

In operation S210, the trim management module 1124 receives the sector address Sector ADDR from the file system 1122 (see FIG. 2). That is, after the delete operation at the upper level with respect to a predetermined file is performed, the file system 1122 provides a sector address (Sector ADDR) for the file to the trim management module 1124.

In operation S220, the trim management module 1124 refers to the group information to determine whether the received sector address is a partial sector address (Partial Sector ADDR). Here, the partial sector address (Partial Sector ADDR) means a sector address that does not coincide with the page unit of the flash memory 1210 (see FIG. 2).

If the received sector address is not a partial sector address (i.e., the received sector address matches a page unit), the trim management module 1124 may apply sector address information (i.e., aligned sector address (i.e. Aligned Sector ADDR) is provided to the flash storage device 1200. If the transferred sector address is a partial sector address (that is, the transferred sector address does not coincide with a page unit), step S240 is performed.

In step S240, it is determined whether a trim management table corresponding to a partial sector address (Partial Sector ADDR) exists. If the trim management table does not exist, the trim management module 1124 generates a trim management table managing the partial sector address (step S250). If the trim management table exists, the trim management module 1124 updates the write state information (WSI) of the trim management table (step S260).

In step S270, it is determined whether all write state information of the trim management table is updated. That is, the trim management module 1124 determines whether all write state information of sectors belonging to the same group are updated as invalid. If all of the write status information is updated to be invalid, the trim management module 1124 may apply the sector address of the corresponding group (ie, the aligned sector address DR) to the flash storage device 1200 along with the trim command TRIM cmd. Provided in step (S280).

As described above, the flash memory system 1000 according to an embodiment of the present invention supports a trim operation. That is, when there is a deletion request for a predetermined file, the host 1100 changes the metadata of the file system 1122 to notify the user that the file has been deleted, and the actual deletion operation is flashed according to a trim command (TRIM cmd). In the storage device 1200. In this case, the host 1100 uses the trim management module 1124 to solve the inconsistency of the management unit between the host 1100 and the flash storage device 1200.

On the other hand, when an erase operation at a higher level is performed on a plurality of files, the trim management module 1124 may be provided with a sector address with a time difference. In this case, the trim management module 1124 may collect address information about sectors requested to be deleted and process the collected address information at one time in idle time. This is described in more detail with reference to FIGS. 14 and 15 below.

III. Host collecting address information of sectors requested for deletion

14 is a diagram illustrating a host that collects information about sector addresses provided at different times and processes information about the collected sector addresses. Except for collecting information about the sector address, the host 1100 described below is similar to the host 1100 of FIG. Therefore, hereinafter, differences from the host 1100 of FIG. 2 will be mainly described. In addition, the same components are described using the same reference numerals.

Referring to FIG. 14, first to third sector addresses Sector ADDR_1 to Sector ADDR_3 are provided to the trim management module 1124. Here, the first to third sector addresses Sector ADDR_1 to Sector ADDR_3 mean sector addresses of different files deleted at higher levels, respectively. In addition, it is assumed that the first to third sector addresses Sector ADDR_1 to Sector ADDR_3 are provided to the trim management module 1124 at different times.

The host memory 1125 includes a sector collection area for collecting provided sector addresses. The trim management module 1124 temporarily stores the first to third sector addresses Sector ADDR_1 to Sector ADDR_3 in the sector collection area of the host memory 1125. At a later idle time (eg, the idle time of the processing unit 1110 (see FIG. 2)), the trim management module 1124 is configured to page out of the collected first to third sector addresses Sector ADDR_1 to Sector ADDR_3. The sector address corresponding to the unit is provided to the flash storage device 1200 (refer to FIG. 2).

For convenience of description, as shown in FIG. 7, it is assumed that the first to third sector addresses Sector ADDR_1 to Sector ADDR_3 correspond to the first to third files File1 to File3, respectively. In this case, since the first to third files File1 to File3 correspond to the first to twelfth sectors Sector1 to Sector3, address information regarding the first to twelfth sectors Sector1 to Sector12 is collected in a sector. It is stored in the Sector Collection Area.

Meanwhile, the first to twelfth sectors Sector1 to Sector12 correspond to page units. That is, the first to fourth sectors Sector1 to Sector4, the fifth to eighth sectors Sector5 to Sector8, and the ninth to twelfth sectors Sector8 to Sector12 each correspond to the same group. Configure

Therefore, at a later idle time, the trim management module 1124 trims the sector address (ie, start sector number '1', number of sectors '12') for the first to twelfth sectors Sector1 to Sector4. The command may be provided to the flash storage device 1200 together with the command TRIM cmd. Since the first to third sector addresses Setor ADDR_1 to Sector ADDR_3 are processed at one time, the host 1100 may process the first to third sector addresses Sector ADDR_1 to Sector ADDR_3 at a time. The transmission time of the trim command to the flash storage device 1200 may be shortened.

FIG. 15 is a flowchart illustrating an operation in which sector addresses for different files are collected in the sector storage area of FIG. 14.

In operation S310, a sector address Sector ADDR is provided to the trim management module 1124 (see FIG. 14). In operation S320, the trim management module 1124 stores the received sector address Sector ADDR in a sector collection area of the host memory 1125 (see FIG. 14). If another sector address is received later, the trim management module 1124 will continue to store the sector address in the sector collection area.

FIG. 16 is a flowchart illustrating an operation of processing sector addresses collected in the sector collection area of FIG. 14 at idle time.

In operation S410, a sector address processing signal SAP is generated. For example, if there is no request from the user for a predetermined time (ie, idle time of the processing unit 1000 (see FIG. 2)), the processing unit 1110 generates a sector address processing signal SAP.

In operation S420, the trim management module 1124 may refer to the flash storage device 1200 (see FIG. 2) along with a trim command of a sector address (that is, an aligned sector address ADDR) corresponding to a page unit among the collected sector addresses. To provide. Since the collected sector addresses are processed at one time, the transmission time of the trim command from the host 1100 to the flash storage device 1200 may be shortened. The sector address processing method of the trim management module 1124 is similar to that of FIG. 13, and thus, detailed description thereof will be omitted.

As described above, when an erase operation at a higher level is performed on a plurality of files, sector addresses for deleted files may be collected in a sector collecting area of the host memory 1124. Since the trim management module 1124 processes the collected sector addresses at once, the transmission time of the trim command from the host 1100 to the flash storage device 1200 may be shortened.

VI. Application example of a flash memory system that handles trim commands

The flash memory system 1000 according to the embodiment of the present invention may be applied or applied to various products. The host 1100 may be configured of a computer, a digital camera, a mobile phone, an MP3 player, a PMP, a game machine, and the like. The flash storage device 1200 may be configured of a solid state drive (SSD), a flash memory card, a flash memory module, or the like based on a flash memory. The host 1100 and the flash storage device 1200 may be connected through a standardized interface such as an ATA, SATA, PATA, USB, SCSI, ESDI, PCI express, or IDE interface.

17 shows an example in which the host 1100 is applied to a memory card according to an embodiment of the present invention. The memory card system 2000 includes a host 2100 and a memory card 2200. The host 2100 includes a host controller 2110 and a host connection unit 2120. The memory card 2200 includes a card connection unit 2210, a card controller 2220, and a flash memory 2230.

The host connection unit 2120 and the card connection unit 2210 are composed of a plurality of pins. These pins include command pins, data pins, clock pins, power pins, and the like. The number of pins depends on the type of memory card 2200. As an example, an SD card has nine pins.

The host 2100 writes data to the memory card 2200 or reads data stored in the memory card 2200. The host controller 2110 may transmit a command (eg, a write command), a clock signal CLK generated by a clock generator (not shown) in the host 2100, and data DAT through the host connection unit 2120. Transfer to memory card 2200.

The card controller 2220 sends data to the memory 2230 in synchronization with a clock signal generated by a clock generator (not shown) in the card controller 2220 in response to a write command received through the card connection unit 2210. Save it. The memory 2230 stores data transmitted from the host 2100. For example, when the host 2100 is a digital camera, image data is stored.

In FIG. 17, the host controller 2110 may include an application program, a file system, and a trim management module that support a trim operation. The card controller 2220 may process a trim command in the memory card 2200 using a flash translation layer. The memory card system illustrated in FIG. 17 may support both the trim operation described above and the management unit matching operation of the trim management module.

18 illustrates an embodiment in which a host is applied to a solid state drive (SSD) according to an embodiment of the present invention. Referring to FIG. 18, the SSD system 3000 includes a host 3100 and an SSD 3200. The SSD 3200 exchanges signals with the host 3100 through a signal connector 3231 and receives power through a power connector 3221. The SSD 3200 includes a plurality of nonvolatile memory devices 3201 to 320n, an SSD controller 3210, and an auxiliary power supply 3220.

The plurality of nonvolatile memory devices 3201 to 320n are used as storage media of the SSD 3200. The plurality of nonvolatile memory devices 3201 to 320n may be implemented as a flash memory device having a large storage capacity. The SSD 3200 mainly uses flash memory.

The plurality of nonvolatile memory devices 3201 to 320n may be connected to the SSD controller 3210 through a plurality of channels CH1 to CHn. One or more memory devices may be connected to one channel. Memory devices connected to one channel may be connected to the same data bus. In this case, the flash defragmentation may be performed in the form of a super block that connects a plurality of memory blocks into one, or in the form of a super page that connects a plurality of pages into one.

The SSD controller 3210 exchanges a signal SGL with the host 3100 through a signal connector 3231. Here, the signal SGL may include a command, an address, data, and the like. The SSD controller 3210 writes data to or reads data from the memory device according to a command of the host 3100. An internal configuration of the SSD controller 3210 will be described in detail with reference to FIG. 19.

The auxiliary power supply 3220 is connected to the host 3100 through a power connector 3221. The auxiliary power supply 3220 may receive the power PWR from the host 3100 and charge it. Meanwhile, the auxiliary power supply 3220 may be located in the SSD 3200 or may be located outside the SSD 3200. For example, the auxiliary power supply 3220 may be located on the main board and provide auxiliary power to the SSD 3200.

FIG. 19 is a block diagram illustrating a configuration of the SSD controller 3210 illustrated in FIG. 18. Referring to FIG. 19, the SSD controller 3210 includes an NVM interface 3211, a host interface 3212, an ECC 3213, a central processing unit (CPU) 3214, and a buffer memory 3215.

The NVM interface 3211 scatters the data transferred from the buffer memory 3215 to the respective channels CH1 to CHn. The NVM interface 3211 transfers the data read from the nonvolatile memory devices 3201 to 320n to the buffer memory 3215. Here, the NVM interface 3211 may use an NAND flash memory interface method. That is, the SSD controller 3210 may perform a program, read, or erase operation according to the NAND flash memory interface method.

The host interface 3212 provides interfacing with the SSD 3200 in correspondence with the protocol of the host 3100. The host interface 3212 uses a host (eg, a universal serial bus (USB), a small computer system interface (SCSI), a PCI express, an ATA, a parallel ATA (PATA), a serial ATA (SATA), or a serial attached SCSI (SAS). 3100). In addition, the host interface 3212 may perform a disk emulation function to support the host 3100 to recognize the SSD 3200 as a hard disk (HDD).

The central processing unit 3214 analyzes and processes the signal SGL input from the host 3100 (see FIG. 19). The central processing unit 3214 controls the host 3100 or the nonvolatile memories 3201 to 320n through the host interface 3212 or the NVM interface 3211. The central processing unit 3214 controls the operations of the nonvolatile memory devices 3201 to 320n in accordance with firmware for driving the SSD 3200.

The buffer memory 3215 temporarily stores write data provided from the host 3100 or data read from the nonvolatile memory device. In addition, the buffer memory 3215 may store metadata or cache data to be stored in the nonvolatile memory devices 3201 to 320n. In the sudden power-off operation, metadata or cache data stored in the buffer memory 3215 is stored in the nonvolatile memory devices 3201 to 320n. The buffer memory 3215 may include DRAM, SRAM, and the like. The solid state drive 3000 illustrated in FIGS. 18 and 19 may be applied to the host described above.

20 is a block diagram illustrating an example in which a host is implemented in a flash memory module according to an example embodiment. Here, a host such as a personal computer (PC), a notebook computer, a mobile phone, a personal digital assistant (PDA), and a camera may be connected to the flash memory module 4100 and used.

Referring to FIG. 20, the flash memory module 4000 may include a memory system 4100, a power supply 4200, an auxiliary power supply 4250, a central processing unit 4300, a RAM 4400, and a user interface 4500. It includes. The flash memory module 4000 illustrated in FIG. 20 may be connected to the host described above and used.

Meanwhile, in the above description, the host 1100 (refer to FIG. 2) manages a file in sectors, and the flash storage device 1200 (refer to FIG. 2) is a flash memory in page units. It is assumed that data stored in 1210 is managed. However, this should be understood as illustrative.

For example, the host 1100 may manage files in a cluster unit, and the flash storage device 1200 may flash in a block unit or a super page unit which is a set of a plurality of pages. Data stored in the memory 1210 may be managed. The management unit of the host 1100 and the flash storage device 1200 may be variously defined by a designer or a data management protocol.

Further, in the above description, it is assumed that the trim management table can be stored in the host memory 1125 (see FIG. 2). When the host memory 1125 is implemented as volatile memory (for example, DRAM), information about the trim management table may be lost due to sudden power off or the like. In this case, since the information about the area managed in the trim management table has been deleted at a higher level, the user may be provided with information that the corresponding data has been deleted regardless of the loss of the information about the trim management table. Meanwhile, the trim management table may be stored in nonvolatile memory (eg, flash memory).

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the above-described embodiments, but should be defined by the equivalents of the claims of the present invention as well as the following claims.

100: memory system 1000: flash memory system
1100: host 1200: flash storage device
2000; Memory card system 3000; SSD system
4000; Flash memory module
TRIM cmd: Trim command Sector ADDR: Sector address
Page ADDR: Page Address Sub_Page ADDR: Sub Page Address
WSI: Write Status Information SAP: Sector Address Processing Signal

Claims (20)

A data management method of a user device for storing data of a file in a data storage device and having a data management unit different from that of the data storage device:
In response to the file deletion request, changing metadata of the file requested to be deleted;
Determining whether information about a storage area of the file requested to be deleted corresponds to a data management unit of the data storage device; And
And transmitting information on an area corresponding to a data management unit of the data storage device, to the data storage device, from among information on a storage area of the file requested to be deleted. The method of claim 1,
The change of the metadata of the file requested to be deleted indicates that the file to be deleted is deleted at a higher level. The method of claim 1,
And generating a trim management table that manages information about an area that does not match a data management unit of the data storage device among information about a storage area of the file requested to be deleted. The method of claim 1,
The information regarding the storage area of the file requested to be deleted is provided from a mapping table of the data storage device. A user device for storing data in a file on a data storage device:
A file system that manages files in a unit different from a data management unit of the data storage device and changes information regarding metadata of a file requested to be deleted; And
And a trim management module configured to provide the data storage device with information about a storage area corresponding to a data management unit of the data storage device among the information about the storage area of the file requested to be deleted. The method of claim 5, wherein
The change of the information about the metadata of the file requested to be deleted indicates that the file requested to be deleted is deleted at a higher level. The method of claim 5, wherein
And a trim management table configured to manage information about an area which does not match a data management unit of the data storage device among information about a storage area of the file requested to be deleted. The method of claim 7, wherein
And a host memory for storing the trim management table, wherein the trim management table stored in the host memory is managed by a push method. The method of claim 5, wherein
And a host memory for storing information about a storage area of at least two files requested to be deleted. The method of claim 9,
The trim management module provides the data storage device with information regarding an area corresponding to a data management unit of the data storage device among information about a storage area of the at least two files requested to be deleted stored in the host memory. . The method of claim 5, wherein
Information regarding the storage area of the file requested to be deleted is provided from a mapping table of the data storage device. A host supporting a trim operation; And
A data storage device for performing an erase operation in response to a trim command from the host,
And the host provides to the data storage device only information on a storage area that matches a data management unit of the data storage device among information on a storage area of a file requested to be deleted. The method of claim 12,
And the host separately manages information about an area that does not match a data management unit of the data storage device among information about a storage area of the file requested to be deleted. The method of claim 12,
The host manages a file on a sector basis, the data storage device manages data of a file on a page basis, and each page is divided into a plurality of sectors. The method of claim 12,
The host is
A file system for managing files on a sector basis and for changing information on metadata of a file requested to be deleted; And
And a trim management module for selecting information about sectors corresponding to a page unit, which is a data management unit of the data storage device, among the sectors of the file to be deleted. The method of claim 15,
The change of the information about the metadata of the file requested to be deleted indicates that the file to be deleted is deleted at a higher level. The method of claim 15,
The host is
And a trim management table that manages information on sectors (hereinafter, partial sectors) that do not match the page unit among sectors of the file requested to be deleted. The method of claim 17,
And the trim management table manages information about the partial sector and information about a sector belonging to the same page as the partial sector. The method of claim 15,
The host is
And a host memory for storing information about sectors of at least two files that are requested to be deleted at different times. The method of claim 19,
And the trim management module selects information on a sector address corresponding to a management unit of the data storage device from among information on sectors of at least two files requested to be deleted at different times stored in the host memory.

Images