TECHNOLOGIES FOR MANAGING ERRORS IN A REMOTELY ACCESSIBLE MEMORY POOL

• US 20190035483A1
• Filed: 12/30/2017
• Published: 01/31/2019
• Est. Priority Date: 08/30/2017
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Schmisseur, Mark, Ziakas, Dimitrios, Nachimuthu, Murugasamy K.
• Granted Patent: US 10,581,596 B2
• Time in Patent Office: Days
• CPC Class Codes: B25J 15/0014 having fork, comb or plate shaped means for engaging the lower surface on a object to be transported
• CPC Class Codes: G06F 1/183 Internal mounting support structures, e.g. for printed circuit boards, internal connecting means for buses G06F13/409
• CPC Class Codes: G06F 1/20 Cooling means
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3442 for planning or managing the needed capacity
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 12/06 Addressing a physical block of locations, e.g. base addressing, module addressing, memory dedication G06F12/08 takes precedence
• CPC Class Codes: G06F 12/0607 Interleaved addressing
• CPC Class Codes: G06F 12/0802 Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
• CPC Class Codes: G06F 12/1054 the data cache being concurrently physically addressed
• CPC Class Codes: G06F 12/1063 the data cache being concurrently virtually addressed
• CPC Class Codes: G06F 12/14 Protection against unauthorised use of memory or access to memory
• CPC Class Codes: G06F 13/1663 Access to shared memory
• CPC Class Codes: G06F 13/1668 Details of memory controller
• CPC Class Codes: G06F 13/4022 using switching circuits, e.g. switching matrix, connection or expansion network G06F13/4009 takes precedence
• CPC Class Codes: G06F 13/4068 Electrical coupling
• CPC Class Codes: G06F 13/42 Bus transfer protocol, e.g. handshake; Synchronisation
• CPC Class Codes: G06F 15/161 Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning casings, cabinets, racks or drawers for data centers H05K5/00
• CPC Class Codes: G06F 15/17331 : Distributed shared memory [DSM], e.g. remote direct memory access [RDMA]
• CPC Class Codes: G06F 15/1735 : Network adapters, e.g. SCI, Myrinet protocol engines H04L69/12
• CPC Class Codes: G06F 15/7807 : System on chip, i.e. computer system on a single chip; System in package, i.e. computer system on one or more chips in a single package
• CPC Class Codes: G06F 15/7867 : with reconfigurable architecture
• CPC Class Codes: G06F 16/119 : Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 16/221 : Column-oriented storage; Management thereof
• CPC Class Codes: G06F 16/2237 : Vectors, bitmaps or matrices
• CPC Class Codes: G06F 16/2255 : Hash tables
• CPC Class Codes: G06F 16/2282 : Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2365 : Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2453 : Query optimisation
• CPC Class Codes: G06F 16/2455 : Query execution
• CPC Class Codes: G06F 16/24553 : of query operations
• CPC Class Codes: G06F 16/248 : Presentation of query results
• CPC Class Codes: G06F 16/25 : Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/9014 : hash tables
• CPC Class Codes: G06F 21/105 : Arrangements for software license management or administration, e.g. for managing licenses at corporate level
• CPC Class Codes: G06F 2200/201 : Cooling arrangements using cooling fluid
• CPC Class Codes: G06F 2201/85 : Active fault masking without idle spares active fault masking without idle spare hardware where processing functionality is redundant G06F11/2035
• CPC Class Codes: G06F 2201/86 : Event-based monitoring
• CPC Class Codes: G06F 2201/885 : Monitoring specific for caches
• CPC Class Codes: G06F 2209/509 : Offload
• CPC Class Codes: G06F 2212/1044 : Space efficiency improvement
• CPC Class Codes: G06F 2212/1052 : Security improvement
• CPC Class Codes: G06F 2212/601 : Reconfiguration of cache memory
• CPC Class Codes: G06F 2213/0026 : PCI express
• CPC Class Codes: G06F 2213/0064 : Latency reduction in handling transfers
• CPC Class Codes: G06F 2213/3808 : Network interface controller
• CPC Class Codes: G06F 3/0604 : Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0605 : by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0611 : in relation to response time
• CPC Class Codes: G06F 3/0613 : in relation to throughput
• CPC Class Codes: G06F 3/0629 : Configuration or reconfiguration of storage systems
• CPC Class Codes: G06F 3/0631 : by allocating resources to storage systems
• CPC Class Codes: G06F 3/0632 : by initialisation or re-initialisation of storage systems
• CPC Class Codes: G06F 3/0644 : Management of space entities, e.g. partitions, extents, pools
• 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/0665 : at area level, e.g. provisioning of virtual or logical volumes
• 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/0673 : Single storage device
• CPC Class Codes: G06F 3/0683 : Plurality of storage devices
• CPC Class Codes: G06F 3/0685 : Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: G06F 30/34 : for reconfigurable circuits, e.g. field programmable gate arrays [FPGA] or programmable logic devices [PLD]
• CPC Class Codes: G06F 9/28 : Enhancement of operational speed, e.g. by using several microcontrol devices operating in parallel
• CPC Class Codes: G06F 9/44 : Arrangements for executing specific programs
• CPC Class Codes: G06F 9/4401 : Bootstrapping security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/4406 : Loading of operating system
• CPC Class Codes: G06F 9/4411 : Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: G06F 9/445 : Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/4494 : data driven
• CPC Class Codes: G06F 9/4856 : resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence
• CPC Class Codes: G06F 9/5044 : considering hardware capabilities
• CPC Class Codes: G06F 9/505 : considering the load
• CPC Class Codes: G06F 9/5061 : Partitioning or combining of resources
• CPC Class Codes: G06F 9/5088 : involving task migration
• CPC Class Codes: G06N 3/063 : using electronic means
• CPC Class Codes: G06Q 10/0631 : Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: G06Q 30/0283 : Price estimation or determination
• CPC Class Codes: G11C 29/028 : with adaption or trimming of parameters
• CPC Class Codes: G11C 29/36 : Data generation devices, e.g. data inverters
• CPC Class Codes: G11C 29/38 : Response verification devices
• CPC Class Codes: G11C 29/44 : Indication or identification of errors, e.g. for repair
• CPC Class Codes: G11C 8/12 : Group selection circuits, e.g. for memory block selection, chip selection, array selection
• CPC Class Codes: H04L 41/0213 : Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/044 : comprising hierarchical management structures
• CPC Class Codes: H04L 41/0668 : by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/0677 : Localisation of faults
• CPC Class Codes: H04L 41/0816 : the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0893 : Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0895 : Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/0896 : Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/14 : Network analysis or design
• CPC Class Codes: H04L 41/142 : using statistical or mathematical methods
• CPC Class Codes: H04L 41/149 : for prediction of maintenance
• CPC Class Codes: H04L 41/16 : using machine learning or artificial intelligence
• CPC Class Codes: H04L 41/34 : Signalling channels for network management communication
• CPC Class Codes: H04L 41/40 : using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5019 : Ensuring fulfilment of SLA
• CPC Class Codes: H04L 41/5025 : by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 43/065 : related to network devices
• CPC Class Codes: H04L 43/0876 : Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 43/16 : Threshold monitoring
• CPC Class Codes: H04L 43/20 : the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 45/28 : using route fault recovery
• CPC Class Codes: H04L 45/7453 : using hashing
• CPC Class Codes: H04L 47/11 : Identifying congestion
• CPC Class Codes: H04L 47/125 : by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/781 : Centralised allocation of resources
• CPC Class Codes: H04L 47/83 : based on usage prediction
• CPC Class Codes: H04L 49/30 : Peripheral units, e.g. input or output ports
• CPC Class Codes: H04L 49/351 : for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 49/40 : Constructional details, e.g. power supply, mechanical construction or backplane
• CPC Class Codes: H04L 49/9005 : using dynamic buffer space allocation
• CPC Class Codes: H04L 63/0428 : wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 67/1001 : for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 : based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 69/12 : Protocol engines
• CPC Class Codes: H04L 69/18 : Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 69/32 : Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/321 : Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 9/0819 : Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) network architectures or network communication protocols for key distribution in a packet data network H04L63/062
• CPC Class Codes: H04L 9/0894 : Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• CPC Class Codes: H05K 7/1489 : characterized by the mounting of blades therein, e.g. brackets, rails, trays H05K7/1491 takes precedence
• CPC Class Codes: H05K 7/1498 : Resource management, Optimisation arrangements, e.g. configuration, identification, tracking, physical location thermal management H05K7/20836
• CPC Class Codes: H05K 7/18 : Construction of rack or frame
• CPC Class Codes: H05K 7/20209 : Thermal management, e.g. fan control
• CPC Class Codes: H05K 7/20736 : within cabinets for removing heat from server blades
• CPC Class Codes: Y02D 10/00 : Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Technologies for managing errors in a remotely accessible memory pool include a memory sled. The memory sled includes a memory pool having one or more byte-addressable memory devices and a memory pool controller coupled to the memory pool. The memory sled is to write test data to a byte-addressable memory region in the memory pool. The memory region is to be accessed by a remote compute sled. The memory sled is also to read data from the memory region to which the test data was written, compare the read data to the test data to determine whether a threshold number of errors are present in the read data, and send, in response to a determination that the threshold number of errors are present in the read data, a notification to the remote compute sled that the memory region is faulty.

Claims

1. A memory sled comprising:

communication circuitry;

a memory pool controller couplable to a memory pool having one or more byte-addressable memory devices, wherein the memory pool controller is to;

(i) write test data to a byte-addressable memory region in the memory pool, wherein the memory region is to be accessed by a remote compute sled through a network;

(ii) read data from the memory region to which the test data was written;

(iii) compare the read data to the test data to determine whether a threshold number of errors are present in the read data; and

(iv) send, in response to a determination that the threshold number of errors are present in the read data, a notification through the network that the memory region is faulty.

2. The memory sled of claim 1, wherein the memory pool controller is further to:

receive, from an orchestrator server, an allocation request to allocate byte-addressable memory from the memory pool to the remote compute sled; and

send, in response to a determination that the threshold number of errors are present in the read data, a second notification to the orchestrator server that the memory region is faulty.

3. The memory sled of claim 1, wherein the memory pool controller is further to:

produce address space data for the remote compute sled, wherein the address space data is indicative of addresses of the byte-addressable memory allocated to the remote compute sled; and

send, to the remote compute sled, the address space data.

4. The memory sled of claim 3, wherein to produce the address space data comprises to produce a contiguous address space from non-contiguous memory addresses in the memory pool.

5. The memory sled of claim 1, wherein the memory pool controller is further to:

allocate, after the notification that the memory region is faulty has been sent, a second memory region of the memory pool for use by the remote compute sled; and

write, to the second memory region of the memory pool, an error-corrected version of the data from the faulty memory region.

6. The memory sled of claim 1, wherein the memory pool controller is further to test all of the memory in the memory pool for faults.

7. The memory sled of claim 1, wherein to determine whether a threshold number of errors are present in the read data comprises to determine whether the number of present errors is within a predefined range of the number of errors that are correctable by an error correction algorithm

8. The memory sled of claim 7, wherein to determine whether more than a number of errors that are correctable by an error correction algorithm are present in the read data comprises to determine whether the number of present errors is within a predefined range of the number of errors that are correctable by a Reed-Solomon error correction algorithm

9. The memory sled of claim 7, wherein to determine whether more than a number of errors that are correctable by an error correction algorithm are present in the read data comprises to determine whether the number of present errors is within a predefined range of the number of errors that are correctable by a low-density parity check error correction algorithm.

10. The memory sled of claim 1, wherein the remote compute sled is one of a plurality of remote compute sleds to which byte-addressable memory from the memory pool has been allocated and the memory pool controller is further to compare an address of the faulty memory region to an address space mapped to each remote compute sled, and wherein to send the notification to the remote compute sled comprises to send the notification to a remote compute sled that has a memory address space to which the faulty memory region is mapped.

11. The memory sled of claim 1, wherein the memory pool controller is further to perform, on the memory pool, a memory access operation for the remote compute sled.

12. The memory sled of claim 11, wherein to perform a memory access operation comprises to write, in response to a memory access request from the remote compute sled, data to the memory pool.

13. One or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a memory sled to:

write test data to a byte-addressable memory region in a memory pool, wherein the memory region is to be accessed by a remote compute sled through a network;

read data from the memory region to which the test data was written;

compare the read data to the test data to determine whether a threshold number of errors are present in the read data; and

send, in response to a determination that the threshold number of errors are present in the read data, a notification through the network that the memory region is faulty.

14. The one or more machine-readable storage media of claim 13, wherein the plurality of instructions further cause the memory sled to:

receive, from an orchestrator server, an allocation request to allocate byte-addressable memory from the memory pool to the remote compute sled; and

send, in response to a determination that the threshold number of errors are present in the read data, a second notification to the orchestrator server that the memory region is faulty.

15. The one or more machine-readable storage media of claim 13, wherein the plurality of instructions further cause the memory sled to:

produce address space data for the remote compute sled, wherein the address space data is indicative of addresses of the byte-addressable memory allocated to the remote compute sled; and

send, to the remote compute sled, the address space data.

16. The one or more machine-readable storage media of claim 15, wherein to produce the address space data comprises to produce a contiguous address space from non-contiguous memory addresses in the memory pool.

17. The one or more machine-readable storage media of claim 13, wherein the plurality of instructions further cause the memory sled to:

allocate, after the notification that the memory region is faulty has been sent, a second memory region of the memory pool for use by the remote compute sled; and

write, to the second memory region of the memory pool, an error-corrected version of the data from the faulty memory region.

18. The one or more machine-readable storage media of claim 13, wherein the plurality of instructions further cause the memory sled to test all of the memory in the memory pool for faults.

19. The one or more machine-readable storage media of claim 13, wherein to determine whether a threshold number of errors are present in the read data comprises to determine whether the number of present errors is within a predefined range of the number of errors that are correctable by an error correction algorithm

20. The one or more machine-readable storage media of claim 19, wherein to determine whether more than a number of errors that are correctable by an error correction algorithm are present in the read data comprises to determine whether the number of present errors is within a predefined range of the number of errors that are correctable by a Reed-Solomon error correction algorithm

21. The one or more machine-readable storage media of claim 19, wherein to determine whether more than a number of errors that are correctable by an error correction algorithm are present in the read data comprises to determine whether the number of present errors is within a predefined range of the number of errors that are correctable by a low-density parity check error correction algorithm.

22. The one or more machine-readable storage media of claim 13, wherein the remote compute sled is one of a plurality of remote compute sleds to which byte-addressable memory from the memory pool has been allocated and the plurality of instructions further cause the memory sled to compare an address of the faulty memory region to an address space mapped to each remote compute sled, and wherein to send the notification to the remote compute sled comprises to send the notification to a remote compute sled that has a memory address space to which the faulty memory region is mapped.

23. A method comprising:

writing, by a memory sled, test data to a byte-addressable memory region of a memory pool, wherein the memory region is to be accessed by a remote compute sled through a network;

reading, by the memory sled, data from the memory region to which the test data was written;

comparing, by the memory sled, the read data to the test data to determine whether a threshold number of errors are present in the read data; and

sending, by the memory sled and in response to a determination that the threshold number of errors are present in the read data, a notification through the network that the memory region is faulty.

24. The method of claim 23, further comprising:

receiving, from an orchestrator server and by the memory sled, an allocation request to allocate byte-addressable memory from the memory pool to the remote compute sled; and

sending, by the memory sled and in response to a determination that the threshold number of errors are present in the read data, a second notification to the orchestrator server that the memory region is faulty.

25. The method of claim 23, further comprising:

producing, by the memory sled, address space data for the remote compute sled, wherein the address space data is indicative of addresses of the byte-addressable memory allocated to the remote compute sled; and

sending, by the memory sled, the address space data to the remote compute sled.