STORAGE APPARATUSES FOR VIRTUALIZED SYSTEM AND METHODS FOR OPERATING THE SAME

• US 20190310794A1
• Filed: 03/26/2019
• Published: 10/10/2019
• Est. Priority Date: 04/05/2018
• Status: Active Grant

• Current Assignee: SungKyunKwan University's Research & Business Foundation (SungKyunKwan University)
• Original Assignee: SungKyunKwan University's Research & Business Foundation (SungKyunKwan University)
• Inventors: EOM, Young Ik, LEE, Hye Ji, LEE, Min Ho
• Granted Patent: US 10,891,073 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0656 Data buffering arrangements
• CPC Class Codes: G06F 3/0679 Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Provided are storage apparatuses for a virtualized system and methods for operating the same. A method for operating a storage apparatus having a write buffer and a memory includes receiving a write request from a virtual machine, identifying a write pattern corresponding to the received write request by comparing a write data size indicated by the write request with a predetermined threshold, and allocating the received write request differently based on the identified write pattern.

Claims

1. A method for operating a storage apparatus having a write buffer and a memory, the method comprising:

receiving a write request from a virtual machine;

identifying a write pattern corresponding to the received write request by comparing a write data size indicated by the write request with a predetermined threshold; and

allocating the received write request differently based on the identified write pattern.

2. The method of claim 1, wherein the method further comprises:

when data related to the received write request is stored in the write buffer, allocating the received write request to a storage location of the related data.

3. The method of claim 2, wherein the method further comprises:

when a remaining capacity is present in the write buffer, allocating the received write request to the write buffer.

4. The method of claim 1, wherein identifying the write pattern corresponding to the received write request is executed when a remaining capacity is absent in the write buffer.

5. The method of claim 1, wherein identifying the write pattern corresponding to the received write request includes:

when the write data size indicated by the received write request exceeds the predetermined threshold, identifying the write pattern corresponding to the received write request as a sequential write pattern.

6. The method of claim 5, wherein allocating the received write request includes:

when the write pattern corresponding to the received write request is identified as the sequential write pattern, allowing the received write request to bypass the write buffer and to be allocated to the memory.

7. The method of claim 1, wherein identifying the write pattern corresponding to the received write request includes:

when the write data size indicated by the received write request is equal to or smaller than the predetermined threshold, identifying the write pattern corresponding to the received write request as a random write pattern.

8. The method of claim 7, wherein allocating the received write request includes:

when the write pattern corresponding to the received write request is identified as the random write pattern, allocating the received write request to the write buffer.

9. The method of claim 7, wherein allocating the received write request includes:

when the write pattern corresponding to the received write request is identified as the random write pattern, deleting data pre-stored in the write buffer and allocating the received write request to a location of the deleted data in the buffer.

10. The method of claim 7, wherein allocating the received write request includes:

when the write pattern corresponding to the received write request is identified as the random write pattern and when the write buffer is based on Least Recently Used (LRU) policy, deleting data in a LRU position in the write buffer, and allocating the received write request to the LRU position of the deleted data.

11. A storage apparatus in a virtualized system, the device comprising:

a write buffer;

a memory; and

a controller for controlling the write buffer and the memory, wherein the controller is configured for;

receiving a write request from a virtual machine;

identifying a write pattern corresponding to the received write request by comparing a write data size indicated by the write request with a predetermined threshold; and

allocating the received write request differently based on the identified write pattern.

12. The device of claim 11, wherein the controller is configured for:

when data related to the received write request is stored in the write buffer, allocating the received write request to a storage location of the related data.

13. The device of claim 12, wherein the controller is configured for:

when a remaining capacity is present in the write buffer, allocating the received write request to the write buffer.

14. The device of claim 11, wherein the controller is configured for:

identifying the write pattern corresponding to the received write request when a remaining capacity is absent in the write buffer.

15. The device of claim 11, wherein the controller is configured for:

when the write data size indicated by the received write request exceeds the predetermined threshold, identifying the write pattern corresponding to the received write request as a sequential write pattern.

16. The device of claim 15, wherein the controller is configured for:

when the write pattern corresponding to the received write request is identified as the sequential write pattern, allowing the received write request to bypass the write buffer and to be allocated to the memory.

17. The device of claim 11, wherein the controller is configured for:

when the write data size indicated by the received write request is equal to or smaller than the predetermined threshold, identifying the write pattern corresponding to the received write request as a random write pattern.

18. The device of claim 17, wherein the controller is configured for:

when the write pattern corresponding to the received write request is identified as the random write pattern, allocating the received write request to the write buffer.

19. The device of claim 17, wherein the controller is configured for:

when the write pattern corresponding to the received write request is identified as the random write pattern, deleting data pre-stored in the write buffer and allocating the received write request to a location of the deleted data in the buffer.

20. A virtualized system comprising:

a host operated by a host operating system;

a virtual machine operated by a guest operating system, wherein the guest operating system operates on top of the host operating system;

a hypervisor located between the virtual machine and the host for controlling a guest operating system accessing a resource of the host operating system; and

a storage apparatus having a write buffer and a memory,

wherein the storage apparatus is configured for;

receiving a write request from a virtual machine;

identifying a write pattern corresponding to the received write request by comparing a write data size indicated by the write request with a predetermined threshold; and

allocating the received write request differently based on the identified write pattern.