System and method for integrating overprovisioned memory devices

• US 10,372,606 B2
• Filed: 09/30/2016
• Issued: 08/06/2019
• Est. Priority Date: 07/29/2016
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Malladi, Krishna, Gim, Jongmin, Zheng, Hongzhong
• Primary Examiner(s): Chery, Mardochee
• Application Number:
  US15/282,848
• Publication Number:
  US 20180032260A1
• Time in Patent Office: 1,040 Days
• Field of Search: 711170
• CPC Class Codes: G06F 12/08 in hierarchically structured memory systems, e.g. virtual memory systems
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 12/10 Address translation
• CPC Class Codes: G06F 2212/1016 Performance improvement
• CPC Class Codes: G06F 2212/152 Virtualized environment, e.g. logically partitioned system
• CPC Class Codes: G06F 2212/401 Compressed data
• CPC Class Codes: G06F 2212/403 Error protection encoding, e.g. using parity or ECC codes

Abstract

A memory device includes a memory interface to a host computer and a memory overprovisioning logic configured to provide a virtual memory capacity to a host operating system (OS). A kernel driver module of the host OS is configured to manage the virtual memory capacity of the memory device provided by the memory overprovisioning logic of the memory device and provide a fast swap of anonymous pages to a frontswap space and file pages to a cleancache space of the memory device based on the virtual memory capacity of the memory device.

Claims

1. A memory device comprising:

a memory interface to a host computer; and

a memory overprovisioning logic configured to provide a virtual memory capacity to a host operating system (OS),

wherein a kernel driver module of the host OS is configured to manage the virtual memory capacity of the memory device provided by the memory overprovisioning logic of the memory device and provide a fast swap of anonymous pages to a frontswap space and file pages to a cleancache space of the memory device based on the virtual memory capacity of the memory device,

wherein the kernel driver module provides a frontswap application programming interface (API) call and a cleancache API call, and

wherein the frontswap API call of the kernel driver module provides a hook to intercept the anonymous pages before the anonymous pages are migrated to a swap space of a secondary swap system, and instead migrates the anonymous pages to the frontswap space of the memory space.

2. The memory device of claim 1, where the virtual memory capacity of the memory device dynamically varies by compression, deduplication, or/and error-correction of data stored in the memory device.

3. The memory device of claim 1, wherein the memory interface is a double data rate (DDR) interface or a peripheral component interconnect express (PCIe) interface.

4. The memory device of claim 1, wherein the frontswap API call of the kernel driver module migrates the anonymous pages to the swap space of the secondary swap system when the virtual memory capacity is full due to a compaction of the memory device.

7. The memory device of claim 1, wherein the frontswap and cleancache API calls initiate a CPU memory copy and direct memory access (DMA) transfer to an interface controller.

8. The memory device of claim 1, wherein the memory overprovisioning logic includes an embedded bitmap to tracks pages in the memory device.

9. The memory device of claim 1, further comprising a dedicated communication channel to provide the virtual memory capacity to the host OS.

5. A memory device comprising:

a memory interface to a host computer; and

a memory overprovisioning logic configured to provide a virtual memory capacity to a host operating system (OS),

wherein a kernel driver module of the host OS is configured to manage the virtual memory capacity of the memory device provided by the memory overprovisioning logic of the memory device and provide a fast swap of anonymous pages to a frontswap space and file pages to a cleancache space of the memory device based on the virtual memory capacity of the memory device,

wherein the kernel driver module provides a frontswap application programming interface (API) call and a cleancache API call, and

wherein the cleancache API call of the kernel driver module provides a hook to intercept the file pages before the file pages are migrated to a file system of a secondary swap system, and instead migrates the file pages to the cleancache space of the memory device.

6. The memory device of claim 5, wherein the cleancache API call of the kernel driver module migrates the file pages to the file system of the secondary swap system when the virtual memory capacity is full due to a compaction ratio of the memory device.

10. A method comprising:

providing a memory device comprising a memory overprovisioning logic configured to provide a virtual memory capacity to a host operating system (OS);

configuring the memory device as a block memory device over a memory interface to a host computer;

loading a kernel driver module from a kernel of the host OS during a runtime; and

providing a fast swap of anonymous pages to a frontswap space and file pages to a cleancache space of the memory device using the kernel driver module based on the virtual memory capacity of the memory device,

wherein the kernel driver module provides a frontswap application programming interface (API) call and a cleancache API call, wherein the frontswap API call of the kernel driver module provides a hook to intercept the anonymous pages before the anonymous pages are migrated to a swap space of a secondary swap system, and instead migrates the anonymous pages to the frontswap space of the memory space, and wherein the cleancache API call of the kernel driver module provides a hook to intercept the file pages before the file pages are migrated to a file system of the secondary swap system, and instead migrates the file pages to the cleancache space of the memory device.

11. The method of claim 10, further comprising registering the memory device as a block memory device having the virtual memory capacity.

12. The method of claim 10, wherein the kernel driver module determines to accept or reject the anonymous pages or the file pages based on the virtual memory capacity.

13. The method of claim 10, where the virtual memory capacity of the memory device dynamically varies by compression, deduplication, or/and error-correction of data stored in the memory device.

14. The method of claim 10, wherein the memory interface is a double data rate (DDR) interface or a peripheral component interconnect express (PCIe) interface.

15. The method of claim 10, wherein the frontswap API call of the kernel driver module migrates the anonymous pages to the swap space of the secondary swap system and the cleancache API call of the kernel driver module migrates the file pages to the file system of the secondary swap system when the virtual memory capacity is full due to a compaction ratio of the memory device.

16. The method of claim 10, wherein the frontswap and cleancache API calls initiate a CPU memory copy and direct memory access (DMA) transfer to an interface controller.

17. The method of claim 10, wherein the memory overprovisioning logic includes an embedded bitmap to tracks pages in the memory device.