HIERARCHICAL PRE-FETCH PIPELINING IN A HYBRID MEMORY SERVER

• US 20190258398A1
• Filed: 02/21/2019
• Published: 08/22/2019
• Est. Priority Date: 06/24/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: CHAN, Yuk Lung, KRISHNAMURTHY, Rajaram B., PARRIS, Carl Joseph
• Granted Patent: US 10,452,276 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 12/0862 with prefetch
• 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 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 2212/264 Remote server
• CPC Class Codes: G06F 2212/602 Details relating to cache prefetching
• CPC Class Codes: G06F 3/0608 Saving storage space on storage systems
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0653 Monitoring storage devices or systems
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: G06F 3/0688 Non-volatile semiconductor memory arrays
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A method, hybrid server system, and computer program product, prefetch data. A set of prefetch requests associated with one or more given datasets residing on the server system are received from a set of accelerator systems. A set of data is prefetched from a memory system residing at the server system for at least one prefetch request in the set of prefetch requests. The set of data satisfies the at least one prefetch request. The set of data that has been prefetched is sent to at least one accelerator system, in the set of accelerator systems, associated with the at least one prefetch request.

Claims

1. A method, on a server system in an out-of-core processing environment, for managing access to data by accelerator systems, the method comprising:

determining a data set to be accessed by at least one accelerator system;

determining one or more characteristics of the data set;

selecting an access configuration from a plurality of different access configurations available for the accelerator system based on the one or more characteristics of the data set, wherein each access configuration of the plurality of different access configurations comprises different parameters indicating how the accelerator system is to access the data set; and

dynamically configuring the accelerator system to access the data set according to the access configuration.

2. The method of claim 1, wherein the data set to be accessed is determined based on a request received from the accelerator system.

4. The method of claim 1, wherein different access configurations are selected for different data sets comprising different characteristics.

5. The method of claim 1, wherein dynamically configuring the accelerator system comprises:

dynamically configuring the accelerator system to one of

access the given data set directly from the server system,

locally store a portion of the given data set in a memory, and

locally store all of the given data set in the memory.

6. The method of claim 5, further comprising:

instructing, in response to dynamically configuring the accelerator system to locally store one of the portion or all of the given data set, the accelerator system to maintain a security counter for the given data set; and

associating a threshold value with the security counter, wherein the threshold value indicates to the accelerator system when to remove the one of the portion or all of the given data set from the memory.

7. The method of claim 1, further comprising:

determining a type of processing core associated with the accelerator system; and

transforming the given data set from a first format to a second format that is associated with the type of processing core that has been determined.

3. The method of 1, wherein determining the one or more characteristics of the data set comprises:

accessing metadata associated with the data set, wherein the metadata is stored in at least one of the data set itself or in a record that is separate from the data set.

8. A server system in an out-of-core processing environment, the server system comprising:

a memory;

a processor communicatively coupled to the memory; and

a data manager communicatively coupled to the memory and the processor, wherein the data manager is configured to perform;

determining a data set to be accessed by at least one accelerator system;

determining one or more characteristics of the data set;

selecting an access configuration from a plurality of different access configurations available for the accelerator system based on the one or more characteristics of the data set, wherein each access configuration of the plurality of different access configurations comprises different parameters indicating how the accelerator system is to access the data set; and

dynamically configuring the accelerator system to access the data set according to the access configuration.

9. The server system of claim 8, wherein the data set to be accessed is determined based on a request received from the accelerator system.

10. The server system of claim 8, wherein determining the one or more characteristics of the data set comprises:

accessing metadata associated with the data set, wherein the metadata is stored in at least one of the data set itself or in a record that is separate from the data set.

11. The server system of claim 8, wherein different access configurations are selected for different data sets comprising different characteristics.

12. The server system of claim 8, wherein dynamically configuring the accelerator system comprises:

dynamically configuring the accelerator system to one of

access the given data set directly from the server system,

locally store a portion of the given data set in a memory, and

locally store all of the given data set in the memory.

13. The server system of claim 8, wherein the data manager is further configured to perform:

determining a type of processing core associated with the accelerator system; and

transforming the given data set from a first format to a second format that is associated with the type of processing core that has been determined.

14. A computer program product for managing accelerator system access to data, the computer program product comprising a non-transitory storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising:

determining a data set to be accessed by at least one accelerator system;

determining one or more characteristics of the data set;

selecting an access configuration from a plurality of different access configurations available for the accelerator system based on the one or more characteristics of the data set, wherein each access configuration of the plurality of different access configurations comprises different parameters indicating how the accelerator system is to access the data set; and

dynamically configuring the accelerator system to access the data set according to the access configuration.

15. The computer program product of claim 14, wherein the data set to be accessed is determined based on a request received from the accelerator system.

16. The computer program product of claim 14, wherein determining the one or more characteristics of the data set comprises:

accessing metadata associated with the data set, wherein the metadata is stored in at least one of the data set itself or in a record that is separate from the data set.

17. The computer program product of claim 14, wherein different access configurations are selected for different data sets comprising different characteristics.

18. The computer program product of claim 14, wherein dynamically configuring the accelerator system comprises:

dynamically configuring the accelerator system to one of

access the given data set directly from the server system,

locally store a portion of the given data set in a memory, and

locally store all of the given data set in the memory.

19. The computer program product of claim 18, wherein the method further comprises:

instructing, in response to dynamically configuring the accelerator system to locally store one of the portion or all of the given data set, the accelerator system to maintain a security counter for the given data set; and

associating a threshold value with the security counter, wherein the threshold value indicates to the accelerator system when to remove the one of the portion or all of the given data set from the memory.

20. The computer program product of claim 14, wherein the method further comprises:

determining a type of processing core associated with the accelerator system; and

transforming the given data set from a first format to a second format that is associated with the type of processing core that has been determined.