Memory deduplication support for remote direct memory access (RDMA)

• US 9,665,534 B2
• Filed: 05/27/2015
• Issued: 05/30/2017
• Est. Priority Date: 05/27/2015
• Status: Active Grant

• Current Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Original Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Inventors: Tsirkin, Michael
• Primary Examiner(s): Yi, David X
• Assistant Examiner(s): Mercado, Ramon A
• Application Number:
  US14/723,033
• Publication Number:
  US 20160350261A1
• Time in Patent Office: 734 Days
• CPC Class Codes: G06F 12/0292 using tables or multilevel address translation means G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10
• CPC Class Codes: G06F 12/145 the protection being virtual, e.g. for virtual blocks or segments before a translation mechanism
• CPC Class Codes: G06F 13/00 Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units interface circuits for specific input/output devices G06F3/00 ; multiprogram control therefor G06F9/46; multiprocessor systems G06F15/16
• CPC Class Codes: G06F 13/28 using burst mode transfer, e.g. direct memory access DMA, cycle steal G06F13/32 takes precedence
• CPC Class Codes: G06F 15/17331 Distributed shared memory [DSM], e.g. remote direct memory access [RDMA]
• CPC Class Codes: G06F 2212/1052 Security improvement

Abstract

An example method of providing deduplication support for remote direct memory access (RDMA) memory includes detecting that a first memory page and a second memory page are identical. A first mapping maps a first virtual memory address (VMA) to a first physical memory address (PMA) of the first memory page. A second mapping maps a second VMA to a second PMA of the second memory page. An RDMA memory region includes the first memory page. The method also includes updating the first mapping to map from the first VMA to the second PMA. The method further includes re-registering the RDMA memory region for RDMA.

Claims

1. A method of providing deduplication support for remote direct memory access (RDMA) memory, comprising:

detecting that a first memory page and a second memory page are identical, wherein a first mapping maps a first virtual memory address (VMA) to a first physical memory address (PMA) of the first memory page, and a second mapping maps a second VMA to a second PMA of the second memory page, wherein the first VMA is part of a first application'"'"'s virtual memory space, and the second VMA is part of a second application'"'"'s virtual memory space, and wherein an RDMA memory region including the first memory page has been registered for RDMA and includes a list of memory pages associated with the first application'"'"'s virtual memory space;

updating the first mapping to map from the first VMA to the second PMA after detecting that the first memory page and the second memory page are identical; and

re-registering the RDMA memory region for RDMA after updating the first mapping.

2. The method of claim 1, further comprising:

determining that the RDMA memory region is set to a read-only permission, wherein the updating and re-registering occur after the RDMA memory region is determined to be set to the read-only permission.

3. The method of claim 1, further comprising:

write-protecting at least one of the first mapping or the second mapping before re-registering the RDMA memory region.

4. The method of claim 1, wherein the list of memory pages specifies physical memory pages included in the RDMA memory region.

5. The method of claim 4, wherein re-registering the RDMA memory region includes updating the list of physical memory pages by replacing the first memory page specified in the list with the second memory page.

6. The method of claim 1, further comprising:

registering the list of memory pages for RDMA, wherein registering includes pinning the list of memory pages; and

un-pinning the first memory page after re-registering the RDMA memory region, wherein re-registering the RDMA memory region includes pinning the second memory page.

7. The method of claim 1, further comprising:

after updating the first mapping, setting the first memory page to a writeable mode.

8. The method of claim 1, further comprising:

reading a flag that indicates whether to send a notification that the first memory page is de-duplicated; and

sending, based on a value of the flag, the notification if the first memory page is de-duplicated.

20. The system of claim 1, wherein after re-registering the RDMA memory region for RDMA, the RDMA memory region includes the second memory page and does not include the first memory page.

9. A system for providing deduplication support for remote direct memory access (RDMA) memory, comprising:

an RDMA memory region that includes a first memory page;

a same page managing module that detects that the first memory page and a second memory page are identical, wherein a first mapping maps a first virtual memory address (VMA) to a first physical memory address (PMA) of the first memory page, and a second mapping maps a second VMA to a second PMA of the second memory page, wherein the first VMA is part of a first application'"'"'s virtual memory space, and the second VMA is part of a second application'"'"'s virtual memory space, and wherein an RDMA memory region including the first memory page has been registered for RDMA and includes a list of memory pages associated with the first application'"'"'s virtual memory space;

a deduplication module that updates the first mapping to map from the first VMA to the second PMA after the same page managing module detects that the first memory page and the second memory page are identical; and

an RDMA core that re-registers the RDMA memory region for RDMA after the deduplication module updates the first mapping.

10. The system of claim 9, wherein a second RDMA memory region includes the second memory page, and the second memory region is set to the read-only permission.

11. The system of claim 9, wherein the second memory page is not registered for RDMA.

12. The system of claim 9, wherein the RDMA core receives a request to register a memory region for RDMA, and the request is from the first application associated with the first memory page, and wherein the RDMA core registers the memory region to produce the RDMA memory region.

13. The system of claim 9, wherein the first application is a guest operating system.

14. The system of claim 9, further comprising:

a second memory that stores a page table for the first application, wherein the page table includes the first mapping.

15. The system of claim 9, wherein the RDMA core sets the first memory page to a writeable mode after the RDMA memory region is re-registered.

16. The system of claim 9, wherein the first memory page is unpinned and the second memory page is pinned after the RDMA memory region is re-registered.

17. The system of claim 9, wherein the deduplication module determines that the RDMA memory region is set to a read-only permission, and wherein the update to the first mapping and the re-registration of the RDMA memory region occur after the RDMA memory region is determined to be set to the read-only permission.

18. The system of claim 9, wherein the deduplication module sets the first mapping to the read-only permission before re-registering the RDMA memory region and sets the second mapping to the read-only permission before re-registering the RDMA memory region.

19. A non-transitory machine-readable medium comprising a plurality of machine-readable instructions that when executed by one or more processors is adapted to cause the one or more processors to perform a method comprising:

detecting that a first memory page and a second memory page are identical, wherein a first mapping maps a first virtual memory address (VMA) to a first physical memory address (PMA) of the first memory page, and a second mapping maps a second VMA to a second PMA of the second memory page, wherein the first VMA is part of a first application'"'"'s virtual memory space, and the second VMA is part of a second application'"'"'s virtual memory space, and wherein an RDM A memory region including the first memory page has been registered for RDM A and includes a list of memory pages associated with the first application'"'"'s virtual memory space;

updating the first mapping to map from the first VMA to the second PMA after detecting that the first memory page and the second memory page are identical; and

re-registering the RDMA memory region for RDM A after updating the first mapping.