WO2022222977A1

WO2022222977A1 - Method and apparatus for managing memory of physical server for running cloud service instances

Info

Publication number: WO2022222977A1
Application number: PCT/CN2022/088044
Authority: WO
Inventors: 汪晶
Original assignee: 华为云计算技术有限公司
Priority date: 2021-04-21
Filing date: 2022-04-21
Publication date: 2022-10-27
Also published as: CN115221073A

Abstract

The present application provides a method and apparatus for managing a memory of a physical server for running cloud service instances. An operating system memory area and a service instance memory area that do not overlap each other are provided in a physical memory of the physical server. The operating system of the physical server runs in the operating system memory area. A memory address range is set for cloud service instances in the service instance memory area, and the memory address range is recorded, wherein the cloud service instances run in the memory address range after being started in the operating system. Since page data structures are generated for the memory in the operating system memory area, but there is no need to generate page data structures for the service instance memory area, the number of the generated page data structures is reduced, and therefore, the space for storing the page data structures is also reduced, and the purpose of providing the physical memory for cloud service instances as much as possible can be achieved.

Description

Memory management method and device for physical server running cloud service instance

technical field

The present application relates to the field of communications, and in particular, to a memory management method and apparatus for running a physical server of a cloud service instance.

Background technique

With the continuous development and maturity of cloud computing, cloud computing products have been widely recognized and used by enterprises, and the memory specifications of physical servers have also been continuously improved with the update and iteration of the central processing unit (CPU).

The operating system allocates 0-4 gigabytes (gigabyte, GB) of virtual memory space for each process, and the virtual memory address in the virtual memory space and the physical memory address in the physical memory are separated, which will give the process no need to care Physical memory addresses bring convenience and security, but the translation of virtual memory addresses and physical memory addresses consumes additional computer resources. The easiest way to record the correspondence between virtual memory addresses and physical memory addresses is to record the correspondence in a table. In order to make the translation speed fast enough, this table must be loaded in memory. However, if the table records each The correspondence between a virtual memory address and a physical memory address is very wasteful.

Therefore, in the prior art, the operating system uses paging to record the corresponding relationship between virtual memory addresses and physical memory addresses. Paging is to manage physical memory with a larger unit "page". The unit of 4KB is for physical memory paging and the page number is set, and the unit of 4 kilobytes (kilobyte, KB) is for virtual memory paging and the page number is set, and each physical memory page corresponds to a 64-byte (byte, B) The page data structure can be used to record the correspondence between the page number of the physical memory and the page number of the virtual memory.

In order to maintain all page data structures, the operating system needs to divide an area from physical memory for storing these page data structures with 64B as the basic unit. According to the 64B page data structure corresponding to each 4KB physical memory block, in order to manage all 4KB physical memory blocks, the operating system needs to use 64B/4KB=1.5625% of the physical memory to store multiple page data structures.

In the public cloud field, cloud service instances run in the operating system of the physical server, and the cloud service instance actually runs on the physical memory allocated by the physical server to the operating system. For the owner of the physical server, that is, for the cloud service provider , the purpose is to provide physical memory for cloud service instances as much as possible, so as to maximize the creation of benefits, but if 1.5625% of the physical memory allocated to the operating system is used to store the page data structure, this is for cloud service providers. It is said to be a waste of physical memory resources.

SUMMARY OF THE INVENTION

In order to solve the above problems, the present application provides a memory management method and device for running a physical server of a cloud service instance, in which non-overlapping operating system memory areas and service instance memory areas are set in the physical memory of the physical server, so as to The operating system allocates the operating system memory area, and allocates the service instance memory area for the cloud service instance in the operating system. Therefore, the page data structure needs to be generated for the memory in the operating system memory area, and the page data structure does not need to be generated for the service instance memory area. Since the number of generated page data structures is reduced, the space for storing the page data structures is also reduced, so as to achieve the purpose of providing physical memory for use by cloud service instances as much as possible.

In a first aspect, the present application provides a memory management method for a physical server. In this method, the physical server sets non-overlapping operating system memory areas and service instance memory areas in the physical memory, sets a memory address range for the cloud service instance in the service instance memory area, and records the memory address range, where the cloud service instance is in The operating system runs in this memory address range after booting. The operating system of the physical server runs in the operating system memory area.

According to the prior art, 1.5625% of the physical memory allocated to the operating system is used to store the page data structure, which occupies the memory quota of the cloud service instance running on the operating system. Based on the physical memory provided to the operating system in the prior art , the embodiment of the present invention divides a special service instance memory area in the physical memory for the cloud service instance, and divides a special operating system memory area for the operating system in the physical memory. The operating system can use 1.5625% of the operating system memory area The page data structure is stored, but the cloud service instance does not run in the operating system memory area, but runs in the service instance memory area, because the operating system memory area is smaller than the physical memory provided to the operating system in the prior art (because it is from In the prior art, the physical memory provided to the operating system is divided), so the number of page data structures to be created is reduced, and the physical memory used to store the page data structures becomes smaller, thereby saving more storage space to Provided for use by cloud business instances.

In a possible implementation, the physical server allocates a cloud service instance identifier to the cloud service instance, applies for a free memory space in the service instance memory area, and uses the address range of the memory space obtained by the application as the memory address range. The cloud service instance identifier and the memory address range of the cloud service instance in the service instance memory area are recorded in the management information area of the service instance memory area.

The memory address range corresponding to different cloud service instances in the service instance memory area can be distinguished by the service instance identifier, so that memory isolation can be achieved between different cloud service instances, and multiple different cloud services can be run simultaneously in the service instance memory area. instance, the memory of multiple cloud service instances does not affect each other. In addition, compared with the memory space occupied by the page data structure corresponding to the memory area of the business instance, the memory space occupied by the management information area is smaller, so that more memory space can be saved for use by the cloud business instance.

In a possible implementation manner, the physical server writes the address corresponding to the memory address range of the cloud service instance in the service instance memory area in the page table of the cloud service instance in the memory area of the operating system.

By writing the address corresponding to the address range of the cloud service instance in the memory area of the service instance into the page table of the cloud service instance in the memory area of the operating system, you can ensure that when the processor starts the cloud service instance in the operating system, it can query the cloud service by querying the cloud service instance. The page table of the instance obtains the address corresponding to the address range of the cloud service instance in the service instance memory area, so that the processor can run the cloud service instance in the service instance memory area according to the obtained address.

In a possible implementation manner, after the operating system is restarted, the physical server rewrites the address corresponding to the memory address range of the cloud service instance in the memory area of the service instance recorded in the memory area of the service instance into the page table of the cloud service instance middle.

After the cloud service provider upgrades the operating system, applies patches, or fixes vulnerabilities, the operating system needs to be restarted. In the prior art, if the operating system is restarted, the data in the physical memory allocated to the operating system will be cleared. Therefore, the data in the physical memory of the cloud service instance running in the operating system will be lost, and in this application , because the cloud service instance runs in the memory area of the service instance instead of the memory area of the operating system, restarting the operating system will only clear the data in the physical memory corresponding to the memory area of the operating system. The data is not affected. After the operating system restarts, by rewriting the address to the page table, it is not necessary to rewrite the relevant data of the cloud service instance into the memory, which can realize the rapid recovery of the cloud service instance.

In a possible implementation manner, the physical server allocates the physical memory of the physical server to the operating system memory area and the service instance memory area in a preset ratio. In this way, the cloud service provider can set a preset ratio according to actual needs, and can manage the memory in a refined manner.

In a possible implementation manner, the physical server may also write the memory address range of the operating system memory area in the physical memory and the memory address range of the business instance memory area in the physical memory into the memory management unit, so as to realize the partition of memory.

In a possible implementation manner, the physical server may also notify the memory management unit to modify the recorded memory address range of the operating system memory area in the physical memory and the memory address range of the operating system memory area in the physical memory, so that the operating system The free memory space in the memory area is added to the service instance memory area, or the free memory space in the service instance memory area is added to the operating system memory area. In this way, the function of adjusting the range of the operating system memory area and the service instance memory area can be realized.

In a possible implementation manner, the physical server generates a page data structure of the operating system memory area during the initialization of the operating system, and the page data structure includes attribute information of memory pages in the operating system memory area. During the initialization process of the operating system, the physical server does not generate the page data structure of the memory area of the service instance. In this way, the initialization speed of the operating system can be accelerated.

In a possible implementation, the physical server traverses the memory management information table in the process of initializing the operating system, determines the memory in the operating system memory area, and establishes a page data structure corresponding to the memory in the operating system memory area. The operating system memory area stores page data structures.

In a possible implementation, the memory management information table is E820. In this way, compatibility can be improved.

In a possible implementation manner, the memory management information table includes: a tag value corresponding to the memory of the memory area of the service instance. The tag value corresponding to the memory of the business instance memory area is used to indicate that the memory belongs to the memory of the business instance memory area. In this way, it can be more compatible with the existing technology.

In a possible implementation, the cloud service instance includes: a virtual machine or a secure container.

In a second aspect, a physical server is provided, where the physical server includes modules for executing the first aspect or any possible implementation manner of the first aspect.

In a third aspect, a physical server is provided, the physical server includes a processor and a memory. The memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions in the memory to perform the operation steps of the method in any possible implementation manner of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to execute the methods of the above aspects.

In a fifth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods of the above aspects.

On the basis of the implementation manners provided by the above aspects, the present application may further combine to provide more implementation manners.

Description of drawings

1 is a schematic diagram of a system architecture according to an embodiment of the present application;

Fig. 2 is the structural representation of a server in Fig. 1;

3 is a schematic diagram of a correspondence between a virtual address and a physical address provided by an embodiment of the present application;

4 is a schematic flowchart of a memory management method for a physical server provided by an embodiment of the present application;

5 is a schematic structural diagram of the physical memory in FIG. 2;

6A is a schematic diagram of adjusting the memory in the business instance memory area in FIG. 3 to the memory in the operating system memory area;

FIG. 6B is a schematic diagram of adjusting the memory in the operating system memory area in FIG. 3 to the memory in the service instance memory area.

Detailed ways

The embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

FIG. 1 exemplarily shows a system architecture to which the embodiments of the present application are applicable. As shown in FIG. 1 , the system may provide a cloud management platform function. Cloud management platform function: Provide access interface (such as interface or Application Programming Interface (API)), tenant can operate client remote access access interface to register cloud account and password in cloud management platform, and log in cloud management platform , after the cloud management platform successfully authenticates the cloud account and password, the tenant can further select and purchase virtual machines of specific specifications (processor, memory, disk) on the cloud management platform. After the payment is successful, the cloud management platform provides the purchased virtual machine The remote login account and password of the virtual machine, the client can remotely log in to the virtual machine, and install and run the tenant's application in the virtual machine.

The logical function division of the cloud management platform: user console, computing management service, network management service, storage management service, authentication service, and image management service. The user console provides interfaces or APIs to interact with tenants, the computing management service is used to manage servers running virtual machines and containers and bare metal servers, the network management service is used to manage network services (such as gateways, firewalls, etc.), and the storage management service is used to manage Manage storage services (such as data bucket services), authentication services are used to manage tenant account passwords, and image management services are used to manage virtual machine images.

Cloud management platform client function: Receive control plane commands sent by the cloud management platform, create on the server according to the control plane control commands, and perform full life cycle management of virtual machines.

Therefore, tenants can create, manage, log in and operate virtual machines in the cloud data center through the cloud management platform.

Among them, a virtual machine (Virtual Machine) refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment. Anything that can be done in a server can be done in a virtual machine. When creating a virtual machine in a server, you need to use part of the hard disk and memory capacity of the physical machine as the hard disk and memory capacity of the virtual machine. Each virtual machine has an independent hard disk and operating system. virtual machine to operate.

Virtual machines can also be called cloud servers (Elastic Compute Service, ECS), elastic instances (different cloud service providers provide different names).

FIG. 2 exemplarily shows a schematic structural diagram of a server in FIG. 1 . In this embodiment of the present application, the server may also be referred to as a physical server. In FIG. 2 , the server 1 in FIG. 1 is used as an example for introduction. It should be noted that the server shown in FIG. 2 may be any server in the system architecture shown in FIG. 1 , and is not limited to server 1 .

As shown in FIG. 2, the server includes a hardware layer and a software layer, and the hardware layer is a conventional configuration of the server, wherein the peripheral component interconnect (PCI) device may be, for example, a network card, a graphics processing unit (graphics processing unit, GPU), offload cards, and other devices that can be plugged into the server's PCI/PCIe slots.

As shown in Figure 2, in the hardware layer, the server may also include a processor and memory. The memory in the server in this embodiment of the present application may also be referred to as physical memory or storage.

Further, the server may further include a bus system, wherein the processor and the physical memory may be connected through the bus system.

The processor can be a chip with signal processing capabilities. For example, the processor may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or a It is a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller unit). , MCU), it can also be a programmable logic device (PLD) or other integrated chips.

In the implementation process, each step of the method in the embodiments of the present application may be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the physical memory, and the processor reads the information in the physical memory, and completes the steps of the method in the embodiment of the present application in combination with its hardware.

It can be understood that the physical memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the physical memory areas described herein are intended to include, but not be limited to, these and any other suitable types of memory.

In this embodiment of the present application, the physical memory may include two memory areas, which are an operating system memory area and a service instance memory area, respectively. The operating system runs in the operating system memory area, and allocates memory for cloud service instances in the service instance memory area.

As shown in FIG. 2 , a memory management unit may also be set in the physical server. The memory management unit may be a memory management unit (memory management unit, MMU) or the like. In some scenarios, the memory management unit can have other names, such as memory manager, memory management module, and so on. A memory management unit refers to a module, unit, or component, etc., used to manage memory. The following describes the memory management unit:

One or more process programs are executed in the operating system, and the address issued by the program is the address of the virtual memory which is not related to the address of the physical memory. That is, the memory address seen in the program is the address of the virtual memory. For example, the virtual memory range is 0-4GB. When the program reads and writes memory, it will be mapped to the actual physical memory. This mapping is called translation. This translation work can be done by Memory management unit (such as MMU) to complete.

For example, the memory management unit can receive the address of the virtual memory page sent by the processor, and find out the address corresponding to the address of the virtual memory page according to the mapping relationship between the address of the virtual memory page recorded in the page table and the address of the physical memory page. The address of the physical memory page, and the address of the found physical memory page is sent to the processor, and the processor reads or writes from the address corresponding to the offset in the physical memory page according to the address and offset of the physical memory page. related data.

As shown in Figure 2, the software layer includes an operating system installed and running on the server (the operating system relative to the virtual machine can be called the host operating system), and the host operating system is provided with a virtual machine manager (virtual machine manager, VMM) (also known as Hypervisor, also known as Virtual Machine Monitor (VMM)). The role of the virtual machine manager is to realize the computing virtualization, network virtualization and storage virtualization of the virtual machine, and is responsible for managing the virtual machine.

The virtual machine manager can virtualize a set of virtual hardware systems independent of real hardware for each virtual machine, such as virtual display, virtual hard disk, virtual processor (Virtual CPU, VCPU), virtual memory, virtual network card, etc. Applications (applications) may be run in the virtual machine based on virtual hardware and a virtual machine operating system, wherein the applications are applications installed and configured by the tenant. In the embodiment of the present application, the virtual machine monitor may run in the operating system memory area mentioned in the embodiment of the present application, or may run in the memory area of the service instance, which is not limited in the embodiment of the present application.

Computing virtualization refers to providing part of the processor and memory of the server to the virtual machine, network virtualization refers to providing some functions of the network card (such as bandwidth) to the virtual machine, and storage virtualization refers to providing part of the disk to the virtual machine. . The virtual machine manager can also achieve logical isolation between different virtual machines and manage virtual machines, such as creating virtual machines, emulating virtual hardware for virtual machines according to the hardware layer (hardware emulation function), deleting virtual machines, forwarding and/or processing running Network packets between all virtual machines on the server (such as virtual machine 1 and virtual machine 2) or forward network packets between virtual machines on the server and external networks (virtual switching function), processing virtual machines Generated I/O, etc.

The running environments (such as virtual machine applications, operating systems, and virtual hardware) in different virtual machines are completely isolated. To communicate between virtual machine 1 and virtual machine 2, network packets need to be forwarded through a virtual manager.

Tenants can log in to the virtual machine remotely, and operate the virtual machine to install, set, and uninstall applications in the virtual machine operating system environment.

As shown in FIG. 2 , two modules may also be set in the virtual machine manager, a module for dividing a memory area and a module for allocating a memory area. The memory area division module can be used to divide the physical memory into the operating system memory area and the service instance memory area. The memory area allocation module can be used to allocate memory for virtual machines. The memory area partitioning module may also be referred to as a random access memory (RAM) partition module, and the memory area allocation module may also be referred to as an instance RAM allocator (instance RAM allocator) module.

It should be understood that the division of the units of the above apparatus is only a division of logical functions, and may be fully or partially integrated into a physical entity in actual implementation, or may be physically separated. In this embodiment of the present application, the memory area allocation module and the memory area division module may be implemented by the processor of FIG. 1 by running program instructions stored in the memory area of the operating system.

As shown in Figure 2, different virtual machines are set for different tenants in the operating system. It should be noted that one physical server can provide multiple virtual machines at the same time, and FIG. 2 only takes two virtual machines as an example for illustration. In practical applications, there is no limit to the number of virtual machines virtualized by one server.

The purpose of memory virtualization technology is to provide virtual machines with a continuous physical memory space starting from address 0, and to effectively isolate and schedule memory resources between virtual machines.

Memory virtualization technology mainly involves guest virtual address (Guest Virtual Address, GVA)—> guest physical address (Guest Physical Address, GPA)—> host virtual address (Host Virtual Address, HVA)—> host physical address ( Host Physical Address, HPA) conversion.

In the virtualization technology, there are often multiple virtual machines running on a physical host, and each virtual machine thinks that it occupies the memory space of the physical host. Therefore, the virtual machine uses the guest physical address (Guest Physical Address, GPA) to represent the virtual machine The memory space owned by the virtual machine, which is considered to be continuous by the virtual machine (that is, it can be understood that the virtual machine thinks that it has a completed physical memory bank).

GVA is the address formed by the virtual machine's operating system mapping GPA. The virtual machine's operating system provides GVA to the process or application software set on the virtual machine's operating system, and the virtual machine's operating system records the GVA to GPA. The mapping relationship, the conversion of GVA to GPA is implemented by the page table of the operating system of the virtual machine.

HPA is the actual physical memory address, HVA is the address formed by the operating system of the host machine mapping the HPA, the operating system of the host machine provides the HVA to the process (such as a virtual machine) on the operating system, and the operating system of the host machine uses the HVA. Record the mapping relationship between HVA and HPA. The conversion from HVA to HPA is implemented by the page table of the operating system of the host.

FIG. 3 exemplarily shows a schematic diagram of a correspondence relationship between a virtual address and a physical address provided by an embodiment of the present application. As shown in Figure 3, virtual machine 1 and virtual machine 2 are set in the same server (hereinafter referred to as the host machine), and the virtual machine manager of the host machine sets the GPA address range of virtual machine 1 to 0-5GB, which corresponds to The HPA address range on physical memory is 1.5GB-4.5GB and 6.5GB-8.5GB. Moreover, the virtual machine manager of the host machine sets the GPA address range of the virtual machine 2 to 0-4GB, which corresponds to the HPA address ranges of 9GB-11GB and 13GB-15GB on the physical memory. Therefore, virtual machine 1 exclusively uses the GPA address range of 0-5GB, and virtual machine 2 exclusively uses the GPA address range of 0-4GB. Both the 0-5GB GPA address range and the 0-4GB GPA address range can correspond to different HPA address ranges on the physical memory, so as to achieve virtual machine memory isolation.

Among them, the GPA address range is related to the virtual machine specifications described above. For example, the tenant can set the virtual machine 1 with a memory size of 5G in the virtual machine specification in the cloud management platform. At this time, the virtual machine manager is notified by the cloud management platform that it needs to Create virtual machine 1 with a GPA of 0-5G.

Based on the above content, FIG. 4 exemplarily shows a schematic flowchart of a memory management method for a physical server provided by an embodiment of the present application. The method may be executed by the virtual machine manager in the host operating system in the above-mentioned FIG. 2 . For another example, the method may be executed by the memory area division module and the memory area allocation module in the virtual machine manager in FIG. 2 . For another example, the method may be executed by the processor shown in FIG. 2, and the related functions of the memory area division module and the memory area allocation module may be implemented by the processor executing program instructions stored in the memory area of the operating system. The method can include:

S201 , the memory area division module is configured to set non-overlapping operating system memory areas and service instance memory areas in the physical memory of the physical server, where the operating system of the physical server runs in the operating system memory area.

S201 may be executed by the aforementioned processor shown in FIG. 2 , and the relevant functions of the memory area division module may be implemented by the processor executing the program instructions stored in the memory area of the operating system.

S202, the memory area allocation module is configured to set a memory address range for the cloud service instance in the service instance memory area, and record the memory address range, where the cloud service instance runs in the memory address range after being started in the operating system.

S202 may be executed by the processor shown in FIG. 2, and the relevant functions of the memory area allocation module may be implemented by the processor executing the program instructions stored in the memory area of the operating system.

In the embodiments of this application, cloud service examples include, but are not limited to: virtual machines (virtual machines, VMs) and containers (containers).

In practical applications, after a piece of memory in the memory area of a business instance is allocated to a cloud business instance, this part of the memory will basically not be used for other purposes until it is released. Based on this, the memory management of the memory area of the business instance by the physical server does not need to be managed by the page data structure. On the other hand, the physical server does not manage the memory in the memory area of the business instance through the page data structure. It seems that many of the benefits brought by the page data structure will be lost in memory management (the benefits brought by the page data structure, for example, can include: fragmentation It can realize advanced features such as memory exchange, merging of the same memory pages, and memory on demand (Populate on demand, POD), etc.), but in fact, since a piece of memory is allocated to a cloud business instance, how does the cloud business instance use it? For this part of memory, the host operating system of the physical server will no longer interfere, nor will the memory in this memory area be used for other purposes. Therefore, even if the physical memory is used for the physical memory area allocated to the cloud service instance Establishing a page data structure does not fully utilize the benefits of the page data structure. Based on the above reasons, the management of the service instance memory area in the embodiment of the present application abandons the management method through the page data structure according to the characteristics of the cloud computing service, thereby saving the page corresponding to the memory used for storing the memory of the cloud service instance The memory of the data structure, based on this scheme, the cloud service provider can provide as much physical memory of the physical server as possible to the tenants, so as to obtain greater benefits.

Further, during the initialization of the operating system, a page data structure of the operating system memory area can be generated, and the page data structure includes attribute information of the memory pages in the operating system memory area, such as physical memory and virtual memory in the operating system memory area. Correspondence between. However, based on the memory partition of the embodiment of the present invention, in the process of initializing the operating system, only the page data structure corresponding to the operating system memory area is generated, and the page data structure of the business instance memory area is not generated. Therefore, the work of generating the page data structure is The amount is reduced, so the operating system initialization startup speed can be accelerated.

In S202, the memory area allocation module may allocate a cloud service instance identifier to the cloud service instance, apply for a free memory space in the memory area of the service instance, and use the address range of the applied memory space as the physical memory of the cloud service instance The memory address range of the cloud service instance and the memory address range of the physical memory of the cloud service instance are recorded in the management information area of the service instance memory area. The content can also be executed by the processor shown in FIG. 2, and the relevant functions of the memory area allocation module can be implemented by the processor executing the program instructions stored in the memory area of the operating system.

Referring to FIG. 5, FIG. 5 exemplarily shows a schematic structural diagram of the physical memory in FIG. 2. As shown in FIG. 5, the physical memory includes an operating system memory area and a service instance memory area. The memory area allocation module can perform memory management based on the management information area in the service instance memory area. The memory area allocation module establishes a management information area in the service instance memory area, and the management information area can be stored in a part of the area demarcated in the service instance memory area.

FIG. 5 also schematically shows the physical memory area allocated by the memory area allocation module for cloud service instance 1 and the memory area allocated for cloud service instance 2 in the service instance memory area. In addition, the service instance memory area may further include free space, such as free space 2 . The memory area allocation module may record the mapping relationship between the identifier of cloud service instance 1 and the memory address range of the physical memory area of cloud service instance 1, and the identifier of cloud service instance 2 and the physical memory area of cloud service instance 2 in the management information area. The mapping relationship of the memory address range.

Continuing to refer to FIG. 5, since the operating system memory area can be used to run the operating system, memory management can be performed based on the page data structure in the operating system memory area, that is, by establishing a page data structure in the operating system memory area, the Management of operating system memory areas. The page data structure may be stored in a portion of an area demarcated in the operating system memory area. In this way, the requirements of the operating environment of the operating system can be complied with. The operating system memory area in FIG. 5 may also include free space, such as free space 1 . A 4KB page in the operating system memory area corresponds to a 64B page data structure, and the page data structure may include the address of the virtual memory corresponding to the address of the physical memory of the 4KB page.

On the one hand, since the cloud service instance identifier and the memory address range of the physical memory of the cloud service instance are recorded through the management information area, the service instance memory area can be managed through the management information area. For example, according to the information recorded in the management information area, you can know which memory in the business instance memory area is allocated to which cloud service instance, and also know which memory in the business instance memory area is in an idle state. In this way, the memory in the memory area of the service instance in the idle state can be allocated to other cloud service instances for use.

On the other hand, the memory address range corresponding to different cloud service instances in the service instance memory area can be distinguished by the service instance identifier, so that memory isolation can be achieved between different cloud service instances, and multiple cloud service instances can be run simultaneously in the service instance memory area. For different cloud service instances, the memory of multiple cloud service instances does not affect each other.

Compared with the memory space occupied by the page data structure corresponding to the memory area of the service instance, the memory space occupied by the management information area is smaller, so that more memory space can be saved for use by the cloud service instance.

When the operating system is restarted, the contents stored in the operating system memory area will be cleared. Since the business instance memory area is not an area that can be used to run the operating system, as the operating system restarts, the business instance memory area will be cleared. content will not be cleared. That is, the data in the memory area of the service instance will not be affected. Therefore, after the operating system is upgraded and restarted, the cloud service instance will not be affected. The cloud service can be quickly restored according to the information stored in the management information area of the memory area of the service instance. For instance, for the cloud service provider, the operating system can be upgraded at any time, and there is no need to worry about the data of the cloud service instance on the tenant side, so it is more convenient.

It is worth noting that the memory area allocation module can set virtual memory for the cloud service instance, and the address range of the virtual memory does not exist in essence, only to make the cloud service instance think that it is running in the memory address range set in the operating system, Therefore, in the above S202, the memory area allocation module may set a memory address range for the cloud service instance in the service instance memory area, and write the memory address of the physical memory of the cloud service instance in the page table of the cloud service instance in the operating system memory area The address corresponding to the range.

For example, the memory area allocation module can first record the memory address of the operating system memory area in the page table of the cloud service instance, and then modify the address in the page table of the cloud service instance so that the address points to the cloud service instance Memory in the business instance memory area. In this way, the compatibility of the embodiments of the present application can be improved. For example, in some solutions, when memory is allocated to a cloud service instance, the cloud service instance is allocated memory that can be used to run the memory area of the operating system. For example, the memory area is not partitioned in the prior art, and the memory range of the physical server that the operating system can run is the same as the memory range that can be allocated to the cloud service instance. For such a solution, the memory of the memory area used for running the operating system can still be allocated to the cloud service instance, and then the address recorded in the page table of the cloud service instance can be modified.

For another example, the memory area allocation module may first record an invalid memory address in the page table of the cloud service instance, and then modify the address so that the address points to the memory of the cloud service instance in the service instance memory area.

For another example, when the cloud service instance is installed, the memory address range of the memory of the cloud service instance in the service instance memory area is recorded in the page table of the cloud service instance. In this way, the steps of modifying the address recorded in the page table of the cloud service instance can be reduced, and the solution can be simplified.

Specifically, the memory area allocation module may record the mapping relationship between the memory address range of the virtual memory of the cloud service instance and the memory address range of the physical memory of the cloud service instance in the page table. The mapping relationship is, for example, the mapping relationship between GVA and HPA in the above-mentioned FIG. 3 .

The cloud service instance can run in the physical memory allocated for the cloud service instance according to the mapping relationship. Specifically, after the cloud service instance is started, the processor running the cloud service instance sends the virtual memory address of the cloud service instance and the identifier of the cloud service instance to the memory management unit. According to the mapping relationship in the page table, the memory management unit can The memory address range of the virtual memory that identifies the corresponding cloud service instance is converted into the memory range of the physical memory, and the processor is notified to access the memory range of the physical memory corresponding to the cloud service instance.

In order to introduce the embodiments of the present application more clearly, a cloud service instance is used as a virtual machine for introduction below.

The program of the virtual machine needs to be installed in the operating system, and after the program of the virtual machine is installed, the operating system can assign a process number to the virtual machine, and can also record the memory address range of the virtual memory of the virtual machine in the page table of the cloud service instance. The mapping relationship with the memory address range of the virtual machine's physical memory. It should be noted that the page table of the cloud service instance refers to a page table used to record the mapping relationship between the address of the virtual memory and the address of the physical memory of the cloud service instance.

When the virtual machine is to be started in the operating system, that is, the processor needs to run the process corresponding to the virtual machine, the processor needs to send the address of the virtual memory corresponding to the process to the memory management unit according to the process ID of the virtual machine, and the memory management unit By querying the page table of the cloud service instance, the address of the physical memory corresponding to the address of the virtual memory can be obtained. Further, the memory management unit sends the found address of the physical memory to the processor, and the processor reads or writes relevant data from the address of the physical memory, so that the processor runs the program of the virtual machine stored in the physical memory the goal of. When the processor runs the program of the virtual machine, the virtual machine can be started.

It should be noted that the page table in the embodiment of the present application is different from the above-mentioned page data structure, and the page table includes the mapping relationship between the memory address range of the virtual memory of the cloud service instance and the memory address range of the physical memory of the virtual machine. , when the processor needs to access the physical memory of the cloud service instance, it can access the physical memory of the cloud service instance by querying the page table through the memory management unit.

However, the page data structure is used to store the attribute information of the memory of the operating system memory area. For example, a 64B page data structure corresponding to a 4KB page may include the address of the virtual memory corresponding to the address of the physical memory of the 4KB page. In this way, when the processor needs to perform a reverse lookup (that is, the processor needs to When searching for the virtual address corresponding to the address of the physical memory), the processor can search according to the information stored in the page data structure.

In addition, the 64B data structure corresponding to the 4KB page can also store other attribute information of the 4KB page, such as: information identifying which NUMA node the 4KB page belongs to, the number of times the 4KB page is referenced in the kernel, and how many times the 4KB page is simultaneously used process sharing and so on.

The page data structure can be stored in the memory area of the operating system, and the page table of the cloud service instance can be stored in the memory area of the operating system or the memory area of the service instance.

When the page table of the cloud service instance is stored in the operating system memory area, when the operating system is restarted, the page table of the cloud service instance will be cleared. Since the information in the memory area of the service instance will not be cleared, after the operating system is restarted, the memory area allocation module can rewrite the address corresponding to the memory address range of the physical memory of the cloud service instance recorded in the memory area of the service instance to the cloud. in the page table of the business instance. Specifically, the memory area allocation module can quickly rebuild the page table of the cloud service instance based on the content recorded in the management information area, thereby speeding up the restarting speed of the operating system.

When the page table of the cloud service instance is stored in the memory area of the service instance, when the operating system is restarted, the page table of the cloud service instance will not be cleared, and then there is no need to rebuild the page table of the cloud service instance, which can speed up the operation. System restart speed.

The memory area dividing module in S201 may allocate the physical memory of the physical server to the operating system memory area and the service instance memory area in a preset ratio. For example, according to the ratio of 3.125%, each 4G physical memory is divided into 128M as the operating system memory area, and 3968M as the business instance memory area.

Optionally, multiple preset ratios may be set, and the memory of physical servers of different specifications may correspond to one of the preset ratios. For example, the memory size required for the operation of the operating system may be determined according to experience, and then the preset ratio may be determined according to the total memory size of the physical server. In this way, the memory space of the memory area of the service instance can be increased as much as possible on the premise of meeting the memory requirements of the operating system, thereby increasing the number of cloud service instances.

In S201, the memory area division module may specifically write the memory address range of the operating system memory area in the physical memory and the memory address range of the business instance memory area in the physical memory into the memory management unit. Specifically, the memory area division module can notify the memory management unit of the memory address range of the operating system memory area in the physical memory and the memory address range of the business instance memory area in the physical memory, and the memory management unit records the operating system in the memory management information table. The memory address range of the memory area in the physical memory and the memory address range of the business instance memory area in the physical memory.

The memory management unit may include a memory management information table. For example, in the process of initializing the operating system (for example, when the physical server is powered on, the operating system is initialized), traverse the memory management information table, determine the memory of the operating system memory area, and establish the memory corresponding to the operating system memory area. Page data structure, which stores the page data structure in the operating system memory area.

Wherein, in the memory management information table of the physical memory, a tag value can be set for a segment of memory, and the tag value can indicate whether the segment of memory belongs to the operating system memory area. In addition, the tag value can also be used to indicate whether the segment of memory belongs to the business instance memory area.

The memory management unit may determine the memory address range belonging to the operating system memory area and the memory address range belonging to the service instance memory area according to the tag value corresponding to the memory in the memory management information table.

Optionally, the memory management information table may specifically be an E820 table. Moreover, in the memory management information table, when a segment of memory belongs to the memory of the operating system memory area, the tag value corresponding to the memory address range of the segment of memory can be set to disable. When a segment of memory is the memory of the business instance memory area, the tag value corresponding to the memory address range of this segment of memory can be set as a new tag value, specifically, it can be distinguished from the existing tag value in the E820 table. The tag value of , for example, the tag value can be defined as "VM".

In the above solution, the memory area division module can dynamically adjust the operating system memory area and the service instance memory area: that is, the memory area division module can convert the memory in the operating system memory area into the memory in the service instance memory area, and the memory area division The module can convert the memory in the business instance memory area into the memory in the operating system memory area.

Specifically, the memory area division module can notify the memory management unit to modify the memory address range of the operating system memory area in the physical memory and the memory address range of the operating system memory area in the physical memory, so as to make the memory area of the operating system free Add the memory space of the service instance to the memory area of the service instance, or add the free memory space in the memory area of the service instance to the memory area of the operating system. The step of notifying the memory management unit may be performed by the aforementioned processor shown in FIG. 2 , and the relevant functions of the memory area division module may be implemented by the processor executing program instructions stored in the memory area of the operating system.

Therefore, through the above solution, the memory of the unused service instance memory area can be adjusted to the operating system memory area. It is worth noting that after this part of the memory is adjusted to the operating system memory area, a page data structure needs to be established for this part of the memory, and memory is allocated from the operating system memory area to store the page data structure.

FIG. 6A exemplarily shows a schematic diagram of adjusting the memory in the memory area of the business instance in FIG. 5 to the memory in the memory area of the operating system. As shown in FIG. 6A , the free space 2 in the memory area of the business instance can be converted into the operating system memory area. Also, the page data structure created for the free space 2 needs to be stored in the operating system memory area.

On the other hand, through the above solution, the unused operating system memory area memory can be adjusted to the business instance memory area. After being adjusted to operate the business instance memory area, the memory occupied by the page data structure corresponding to this part of the memory is released. .

FIG. 6B exemplarily shows a schematic diagram of adjusting the memory space in the operating system memory area in FIG. 5 to the memory of the service instance memory area. As shown in FIG. 6B , the free space 1 can be converted from the operating system memory area to the service instance memory area of memory. Correspondingly, the memory space occupied by the page data structure corresponding to the free space 1 in the operating system memory area can be released.

Further, the memory area allocation module may record the usage status of the memory of the business instance memory area in the management information area, and the usage status of the memory may include an occupied status and an idle status. When a memory block is marked as occupied, it means that the memory block is allocated for use by the cloud service instance. When the memory block is marked as free, it means that the memory block is not currently allocated to the cloud service instance. When there is a memory allocation requirement, the memory block can be allocated to the cloud service instance.

For example, the usage status of the memory can be recorded by means of bits (ie, bitmap). For example, the memory area of a business instance is 512GB, and one bit is used to represent a memory block with a size of 1GB (it can also be a memory block of other size, such as a 4M memory block). In the occupied state, the bit position corresponding to the memory block can be set to 1, and if the memory block is in an idle state, the bit position corresponding to the memory block can be set to 0. It can be seen that in this method, a certain number of bits can be used to manage the memory of the business memory area. Compared with the method of building a page data structure to manage the memory, the storage space occupied by the management information area is smaller, so it can be further Save more storage space.

In other examples, the usage status of the memory block may be recorded by recording the memory address range. For example, if "00000000aafe8000-00000000aaffd000" is allocated for use by cloud service instance 1, the information that "00000000aafe8000-00000000aaffd000" is occupied can be recorded in the management information area. It can be seen that in this method, the memory of the business memory area can be managed by recording the starting address of the memory block and the usage status of the memory block. Compared with the method of establishing a page data structure to manage the memory, the management information area occupies more The storage space is smaller, so it can further save more storage space.

It is worth noting that when the memory area division module can adjust the memory of the unused service instance memory area to the operating system memory area, the memory area allocation module can record the usage status of this part of the memory area in the management information area. For example, in FIG. 6B above, when the memory area division module adjusts the free space 1 to the service instance memory area, the memory area allocation module can record information such as the free space 1 is currently in an idle state in the management information area.

Further, the management information area also includes NUMA affinity information of the cloud service instance in the memory area of the service instance memory area. In this embodiment of the present application, the NUMA affinity information may be information of a NUMA node managed by the memory, such as information of a processing core associated with the NUMA node, information of a NUMA node number to which the memory belongs, and the like.

Further, in S202, the memory area allocation module may allocate memory for the cloud service instance, and the name of the method for allocating memory may be called in a variety of ways, for example, it may be called a class partner algorithm. The name is not qualified. The method of allocating memory is described below through an example: For example, the memory area of a business instance is 512 GB, and cloud business instance 1 needs 100 GB of memory, so the 100 GB memory block is allocated to the cloud business instance 1. After that, when cloud service instance 2 requests a 20 GB memory block, 20 GB of memory is allocated to cloud service instance 2 from the memory in the idle state of the memory area of the service instance. After the cloud service instance 1 no longer needs memory, you can release the 100 GB memory block occupied by the cloud service instance 1, and update the usage status of the 100 GB memory block from the occupied state to the idle state in the management information area.

According to the method provided by the embodiments of the present application, the present application also provides a computer program product, the computer program product includes: computer program code or instructions, when the computer program code or instructions are run on a computer, the computer is made to execute FIG. 4 Relevant method steps involved in S201 and S202.

According to the method provided by the embodiment of the present application, the present application further provides a computer-readable storage medium, where the computer-readable medium stores program codes, and when the program codes are executed on a computer, the computer is made to execute S201 and S201 in FIG. 4 . Relevant method steps involved in S202.

According to the method provided by the embodiment of the present application, the present application further provides a chip system, where the chip system may include a processor. The processor is coupled to the memory and can be used to execute the relevant method steps involved in S201 and S202 in Fig. 4 . Optionally, the chip system further includes a memory. Memory, used to store computer programs (also called code, or instructions). The processor is used to call and run the computer program from the memory, so that the device with the chip system installed performs the relevant method steps involved in S201 and S202 in FIG. 4 .

At least one involved in the embodiments of the present application includes one or more; wherein, multiple refers to greater than or equal to two. In addition, in the description of this application, words such as "first" and "second" are only used for the purpose of distinguishing the description objects, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

It should be understood that the terms "first", "second", "third", "fourth", "fifth" and "sixth" in this application are used to distinguish similar objects, and are not necessarily used for description a particular order or sequence. "And/or" is used to describe the relationship between related objects, indicating that there can be three kinds of relationships, for example, "A and/or B" can mean: only A, only B, and both A and B exist , where A and B can be singular or plural. The character "/" generally indicates that the associated objects are an "or" relationship.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When computer instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. Computer instructions may be stored on or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g. coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to transmit to another website site, computer, server or data center. A computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media. Useful media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, high-density digital video disc (DVD)), or semiconductor media (eg, solid state disc (SSD)) )Wait.

It should be noted that a part of this patent application file contains content protected by copyright. Except for making copies of the patent files of the Patent Office or the contents of the recorded patent files, the copyright owner reserves the right to copyright.

The network equipment in the above apparatus embodiments corresponds to the terminal equipment and the network equipment or terminal equipment in the method embodiments, and corresponding steps are performed by corresponding modules or units, for example, the communication unit (transceiver) performs the receiving or sending in the method embodiments. The steps other than sending and receiving can be performed by the processing unit (processor). For functions of specific units, reference may be made to corresponding method embodiments. The number of processors may be one or more.

The terms "component", "module", "system" and the like are used in this specification to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be components. One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware accomplish. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The functions, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer-readable storage medium.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, and should cover within the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A memory management method for running a physical server of a cloud service instance, comprising:

A non-overlapping operating system memory area and a service instance memory area are set in the physical memory of the physical server, wherein the operating system of the physical server runs in the operating system memory area;

A memory address range is set for the cloud service instance in the service instance memory area, and the memory address range is recorded, wherein the cloud service instance runs in the memory address range after being started in the operating system.
The method according to claim 1, wherein the setting a memory address range for the cloud service instance in the service instance memory area comprises:

assigning a cloud service instance identifier to the cloud service instance;

Apply for a section of free memory space in the business instance memory area, and use the address range of the memory space obtained by the application as the memory address range;

The cloud service instance identifier and the memory address range are recorded in the management information area of the service instance memory area.
The method according to claim 1 or 2, wherein the method further comprises:

Write the address corresponding to the memory address range in the page table of the cloud service instance in the operating system memory area.
The method according to claim 3, wherein the method further comprises:

After the operating system is restarted, the address corresponding to the memory address range recorded in the memory area of the service instance is rewritten into the page table of the cloud service instance.
The method according to any one of claims 1 to 4, wherein the setting of the operating system memory area and the service instance memory area in the physical memory of the physical server includes:

Allocate the physical memory of the physical server to the operating system memory area and the service instance memory area in a preset ratio.
The method according to any one of claims 1-5, wherein the setting of the operating system memory area and the service instance memory area in the physical memory of the physical server further comprises:

Write the memory address range of the operating system memory area in the physical memory and the memory address range of the service instance memory area in the physical memory into the memory management unit.
The method according to claim 6, wherein the method further comprises:

Notify the memory management unit to modify the recorded memory address range of the operating system memory area in the physical memory and the memory address range of the operating system memory area in the physical memory, so that the operating system memory area The free memory space is added to the service instance memory area, or the free memory space in the service instance memory area is added to the operating system memory area.
A physical server for running a cloud service instance, comprising:

a memory area dividing module, configured to set non-overlapping operating system memory areas and business instance memory areas in the physical memory of a physical server, wherein the operating system of the physical server runs in the operating system memory area;

A memory area allocation module, configured to set a memory address range for the cloud service instance in the service instance memory area, and record the memory address range, wherein the cloud service instance runs in the cloud service instance after being started in the operating system. range of memory addresses.
The physical server according to claim 8, wherein the memory area allocation module is specifically used for:

assigning a cloud service instance identifier to the cloud service instance;

Apply for a section of free memory space in the business instance memory area, and use the address range of the memory space obtained by the application as the memory address range;

The cloud service instance identifier and the memory address range are recorded in the management information area of the service instance memory area.
The physical server according to claim 9, wherein the memory area allocation module is further configured to:

Write the address corresponding to the memory address range in the page table of the cloud service instance in the operating system memory area.
The physical server according to claim 10, wherein the memory area allocation module is further configured to:

After the operating system is restarted, the address corresponding to the memory address range recorded in the memory area of the service instance is rewritten into the page table of the cloud service instance.
The physical server according to any one of claims 8 to 11, wherein the memory area division module is specifically used for:

Allocate the physical memory of the physical server to the operating system memory area and the service instance memory area in a preset ratio.
The physical server according to any one of claims 8-12, wherein the memory area division module is further configured to:

Write the memory address range of the operating system memory area in the physical memory and the memory address range of the service instance memory area in the physical memory into the memory management unit.
The physical server according to claim 13, wherein the memory area division module is further configured to:

Notify the memory management unit to modify the recorded memory address range of the operating system memory area in the physical memory and the memory address range of the operating system memory area in the physical memory, so that the operating system memory area The free memory space is added to the service instance memory area, or the free memory space in the service instance memory area is added to the operating system memory area.
A physical server for running a cloud service instance, comprising a processor and a physical memory, wherein the physical memory stores program instructions, and the processor executes the program instructions to execute the following method:

A non-overlapping operating system memory area and a service instance memory area are set in the physical memory of the physical server, wherein the operating system of the physical server runs in the operating system memory area;

A memory address range is set for the cloud service instance in the service instance memory area, and the memory address range is recorded, wherein the cloud service instance runs in the memory address range after being started in the operating system.