Scheduling of data migration

• US 9,594,521 B2
• Filed: 02/23/2015
• Issued: 03/14/2017
• Est. Priority Date: 02/23/2015
• Status: Active Grant

• Current Assignee: Advanced Micro Devices, Inc.
• Original Assignee: Advanced Micro Devices, Inc.
• Inventors: Blagodurov, Sergey, Kegel, Andrew G.
• Primary Examiner(s): Ruiz, Aracelis
• Application Number:
  US14/629,014
• Publication Number:
  US 20160246540A1
• Time in Patent Office: 750 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0215 with look ahead addressing means
• CPC Class Codes: G06F 12/1081 for peripheral access to main memory, e.g. direct memory access [DMA]
• CPC Class Codes: G06F 2212/654 Look-ahead translation
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0611 in relation to response time
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

In one form, scheduling data migration comprises determining whether the data is likely to be used by an input/output (I/O) device, the data being at a location remote to the I/O device; and scheduling the data for migration from the remote location to a location local to the I/O device in response to determining that the data is likely to be used by the I/O device.

Claims

1. A method of scheduling data migration comprising:

determining whether the data is likely to be used by an input/output (I/O) device, the data being at a location remote to the I/O device; and

scheduling the data for migration from the remote location to a location local to the I/O device in response to determining that the data is likely to be used by the I/O device, wherein determining that the data is likely to be used by the I/O device comprises monitoring an event associated with translating addresses by a memory management unit local to the I/O device,

wherein monitoring the event associated with translating addresses by the memory management unit local to the I/O device includes one or more of;

monitoring data having a memory address in a peripheral page service request event log file, monitoring data having a memory address in an error event log file, and monitoring data having a memory address in a command issued by the I/O device to invalidate the data.

2. The method of claim 1, wherein scheduling the data for migration includes:

determining, in response to determining that the data is likely to be used by the I/O device, whether the data is to be migrated; and

scheduling the data for migration in response to determining that the data is to be migrated.

3. The method of claim 2, wherein data that is to be migrated includes data that is not being used by a remote device at the remote location.

4. The method of claim 3, wherein the remote device includes a memory management unit (MMU).

5. The method of claim 1, wherein data that is likely to be used by the I/O device includes data in which the I/O device has previously expressed an interest.

6. The method of claim 5, wherein data in which the I/O device has previously expressed an interest includes data having a memory address in a command issued by the I/O device to pre-fetch the data.

7. A data processing node comprising:

a data processor; and

an input/output memory management unit (IOMMU) coupled to the data processor and adapted to associate logical memory pages to corresponding physical pages wherein each physical page may be located in either a local memory device associated with the data processing node or in a remote memory device associated with another processing node, wherein the IOMMU is adapted to determine whether data in a physical page in the remote memory device is likely to be used by an input/output (I/O) device coupled to and associated with the processing node, and in response to determining that the data is likely to be used by the I/O device, to schedule migration of the data in the physical page at the remote memory device to a physical page at the local memory device,

wherein the IOMMU determines that data is likely to be used by the I/O device by monitoring the output of at least one address translation circuit associated with the I/O device, and

wherein the IOMMU monitors the output of the at least one address translation circuit associated with the I/O device by monitoring a memory address in a log file.

8. The data processing node of claim 7, wherein the IOMMU is further adapted to determine, in response to determining that the data is likely to be used by the I/O device, whether the data can be migrated, and to schedule migration of the data in the physical page at the remote memory device to the physical page at the local memory device in response to determining that the data can be migrated.

9. The data processing node of claim 8, wherein data that can be migrated includes data that is not being used by a remote device at a remote location.

10. The data processing node of claim 8, wherein the remote device includes a memory management unit (MMU).

11. The data processing node of claim 8, wherein data likely to be used by the I/O device includes data having a memory address in a command issued by the I/O device to pre-fetch the data.

12. The data processing node of claim 8, wherein the IOMMU monitors the output of the at least one address translation circuit associated with the I/O device by monitoring a memory address in a peripheral page service request event log file.

13. The data processing node of claim 8, wherein the IOMMU monitors the output of the at least one address translation circuit associated with the I/O device by monitoring a memory address in an error event log file.

14. A data processing node comprising:

a data processor; and

an input/output memory management unit (IOMMU) coupled to the data processor and adapted to associate logical memory pages to corresponding physical pages wherein each physical page may be located in either a local memory device associated with the data processing node or in a remote memory device associated with another processing node, wherein the IOMMU is adapted to determine whether data in a physical page in the remote memory device is likely to be used by an input/output (I/O) device coupled to and associated with the processing node, and in response to determining that the data is likely to be used by the I/O device, to schedule migration of the data in the physical page at the remote memory device to a physical page at the local memory device,

wherein the IOMMU determines that data is likely to be used by the I/O device by monitoring the output of at least one address translation circuit associated with the I/O device, and

wherein the IOMMU monitors the output of the at least one address translation circuit associated with the I/O device by monitoring a memory address in a command issued by the I/O device to invalidate the data.