Node controller based request response method and device

Abstract

An embodiment of the invention discloses a node controller based request response method and device. The method includes receiving a first message through a first node controller; acquiring an information catalog, and inquiring in the information catalog to confirm whether a memory address requested in the first message is occupied by a second node controller or not; if yes, inquiring node in-place information to determine whether the second node controller exists or not; if not, generating and sending an invalid response message; wherein, a destination node number DNID (destination node identity) of the invalid response message is a source node number SNID (source node identity) of the first message, and an SNID of the invalid response message is a DNID of the first message.

Description

technical field [0001] The present invention relates to the field of communication technology, in particular to a node controller-based request response method and device. Background technique [0002] The modern advanced features of the system architecture enable the processor (CPU) to have error reporting and error correction capabilities, and support CPU hot-swappable technology. Some foundry manufacturers already support non-uniform memory access (Non-Uniform Memory Access, NUMA) hardware hot-swapping, that is, the insertion and removal of physical nodes. This advanced feature requires the kernel to be able to remove in-use CPUs when necessary. For example, a CPU executing malicious code must be kept out of the system's execution path for Remote Access Service (RAS) requirements. Therefore, it is necessary to support CPU hot-plug technology in the Linux kernel. The operating system (OS) offlines the CPU logic, and the operating system will no longer use the offline CP...

AI Technical Summary

Problems solved by technology

[0021] However, when using this method to remove a node, other nodes need to refresh the local memory, so it takes up a lot of OS usage time, which will cause the system to respond very slowly and greatly reduce system performance.

In the actual measurement, if the 256Gb memory in a single node is refreshed, and the BIOS takes up 60-70% of the time slice of the CPU, it takes about 20 minutes to complete. During this period, the response of the OS becomes very slow, which is basically unacceptable to users

And the larger the single-node memory, the larger the system scale, the longer it takes to refresh the memory

Images