MULTI-STREAMED SOLID STATE DRIVE

• US 20160283125A1
• Filed: 03/09/2016
• Published: 09/29/2016
• Est. Priority Date: 03/25/2015
• Status: Abandoned Application

• Current Assignee: Toshiba Memory Corporation (Kioxia Corporation)
• Original Assignee: Kabushiki Kaisha Toshiba (Toshiba Corporation)
• Inventors: HASHIMOTO, Daisuke, KANNO, Shinichi
• Application Number:
  US15/065,496
• Publication Number:
  US 20160283125A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 16/164 File meta data generation
• CPC Class Codes: G06F 16/166 File name conversion
• CPC Class Codes: G06F 16/1847 specifically adapted to static storage, e.g. adapted to flash memory or SSD
• CPC Class Codes: G06F 2212/1016 Performance improvement
• CPC Class Codes: G06F 2212/1036 Life time enhancement
• CPC Class Codes: G06F 2212/214 Solid state disk
• CPC Class Codes: G06F 2212/7201 Logical to physical mapping or translation of blocks or pages
• CPC Class Codes: G06F 2212/7205 Cleaning, compaction, garbage collection, erase control
• CPC Class Codes: G06F 3/0613 in relation to throughput
• CPC Class Codes: G06F 3/0616 in relation to life time, e.g. increasing Mean Time Between Failures [MTBF]
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/0643 Management of files
• CPC Class Codes: G06F 3/0679 Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A storage system includes a drive having a nonvolatile semiconductor memory device including a plurality of physical blocks and a controller configured to control access to the nonvolatile semiconductor memory device, and a host connected to the memory drive through an interface and access the drive in accordance with an operation of a file system driver executing in the host. When a file is updated, the file system driver operates to determine an identifier based on a file name or a file extension of the file and transmit a write command, the identifier, and update data for the file to the drive. Upon receiving the write command, the identifier, and the update data for the file, the controller is configured to write the update data into a physical block associated with the identifier.

Claims

1. A storage system, comprising:

a drive having a nonvolatile semiconductor memory device including a plurality of physical blocks and a controller configured to control access to the nonvolatile semiconductor memory device; and

a host connected to the drive through an interface and access the drive in accordance with an operation of a file system driver executing in the host, wherein

when a file is updated, the file system driver operates to determine an identifier based on a file name or a file extension of the file and transmit a write command, the identifier, and update data for the file to the drive, and

upon receiving the write command, the identifier, and the update data for the file, the controller is configured to write the update data into a physical block associated with the identifier.

2. The storage system according to claim 1, wherein

when the identifier is determined to be a first identifier, the update data are written into a physical block associated with the first identifier, and

when the identifier is determined to be a second identifier different from the first identifier, the update data are written into another physical block associated with the second identifier.

3. The storage system according to claim 1, wherein

the file system driver operates to manage mapping between each of file names and an identifier or between each of file extensions and an identifier, and the determination of the identifier is carried out by referring to the mapping.

4. The storage system according to claim 1, wherein

the determination of the identifier is carried out by calculation of a value of the identifier from the file name or the file extension.

5. The storage system according to claim 4, wherein

the value of the identifier equals to a remainder obtained by dividing a numerical value resulting from converting the file name or the file extension using a hash function, with a number of streams established by the file system driver.

6. The storage system according to claim 1, wherein

when the file name is a first file name, a first identifier is determined as the identifier, and

when the file name is a second file name different from the first file name, a second identifier that is different from the first identifier is determined as the identifier.

7. The storage system according to claim 6, wherein

when the file name is a third file name different from the first and second names, the first identifier is determined as the identifier.

8. The storage system according to claim 1, wherein

when the file extension is a first file extension, a first identifier is determined as the identifier, and

when the file extension is a second file extension different from the first file extension, a second identifier that is different from the first identifier is determined as the identifier.

9. The storage system according to claim 8, wherein

when the file extension is a third file extension different from the first and second extensions, the first identifier is determined as the identifier.

10. A storage system, comprising:

a drive having a nonvolatile semiconductor memory device including a plurality of physical blocks and a controller configured to control access to the nonvolatile semiconductor memory device; and

a host connected to the drive through an interface and access the drive in accordance with an operation of a file system driver executing in the host, wherein

when a file is updated, the file system driver operates to determine an identifier based on a user name of a user who operates to store update data for the file in the drive and transmit a write command, the identifier, and the update data for the file to the drive, and

upon receiving the write command, the identifier, and the update data for the file, the controller is configured to write the update data into a physical block associated with the identifier.

11. The storage system according to claim 10, wherein

when the identifier is determined to be a first identifier, the update data are written into a physical block associated with the first identifier, and

when the identifier is determined to be a second identifier different from the first identifier, the update data are written into another physical block associated with the second identifier.

12. The storage system according to claim 10, wherein

the file system operates to manage mapping between each of user names and an identifier, and the determination of the identifier is carried out by referring to the mapping.

13. The storage system according to claim 10, wherein

the determination of the identifier is carried out by calculation of a value of the identifier from the user name.

14. The storage system according to claim 13, wherein

the value of the identifier equals to a remainder obtained by dividing a numerical value resulting from converting the user name using a hash function, with a number of streams established by the file system.

15. The storage system according to claim 10, wherein

when the user name is a first user name, a first identifier is determined as the identifier, and

when the user name is a second user name different from the first user name, a second identifier that is different from the first identifier is determined as the identifier.

16. A storage system, comprising:

a memory having a nonvolatile semiconductor memory device including a plurality of physical blocks and a controller configured to control access to the nonvolatile semiconductor memory device; and

a host connected to the drive through an interface and access the drive in accordance with an operation of a file system driver executing in the host, wherein

when a file is updated, the file system driver operates to determine an identifier based on an identifier of an application, a virtual machine, or a thread that operates to write update data for the file in the drive and transmit a write command, the identifier, and the update data for the file to the drive, and

upon receiving the write command, the identifier, and the update data for the file, the controller is configured to write the update data into a physical block associated with the identifier.

17. The storage system according to claim 16, wherein

when the identifier is determined to be a first identifier, the update data are written into a physical block associated with the first identifier, and

when the identifier is determined to be a second identifier different from the first identifier, the update data are written into another physical block associated with the second identifier.

18. The storage system according to claim 16, wherein

the file system operates to manage mapping between each of names of applications, virtual machines, and threads and an identifier, and the determination of the identifier is carried out by referring to the mapping.

19. The storage system according to claim 16, wherein

the value of the identifier equals to a remainder obtained by dividing a numerical value resulting from converting the name of the application, the virtual machine, or the thread using a hash function with a number of streams established by the file system.

20. The storage system according to claim 16, wherein

when the name of the application, the virtual machine, or the thread is a first name, a first identifier is determined as the identifier, and

when the name of the application, the virtual machine, or the thread is a second name different from the first name, a second identifier that is different from the first identifier is determined as the identifier.