WO2022100208A1

WO2022100208A1 - Dynamic library loading method, kernel deployment adjustment method, and related apparatuses

Info

Publication number: WO2022100208A1
Application number: PCT/CN2021/115233
Authority: WO
Inventors: 欧炜; 陈计亮; 江维财; 徐高峰
Original assignee: 华为技术有限公司
Priority date: 2020-11-13
Filing date: 2021-08-30
Publication date: 2022-05-19
Also published as: CN114489827A; CN114489827B

Abstract

A dynamic library loading method, a kernel deployment adjustment method, and related apparatuses. The dynamic library loading method comprises: when a first application is loaded in a target kernel, obtaining, from a file system, executable files of all dynamic libraries to be loaded corresponding to the target kernel, wherein the executable file of a dynamic library that is associated with a first platform dynamic library version in the executable files of all said dynamic libraries is the latest dynamic library version of a platform that supports the loading of the first application; respectively pre-linking and then storing the executable files of all said dynamic libraries; and then acquiring a pre-linked executable file of each of said dynamic libraries, and loading the pre-linked executable file of each of said dynamic libraries into the target kernel. Therefore, during each subsequent instance that a first application needs to be switched and loaded on a target kernel, a pre-linked executable file that is compatible with and matches the latest dynamic library version of a platform can be directly obtained from a file system, such that the problem of a loading failure of a dynamic library is prevented.

Description

Dynamic library loading method, core deployment adjustment method and related device

This application claims the priority of the Chinese patent application filed on November 13, 2020 with the State Intellectual Property Office of the People's Republic of China, the application number is 202011268494.3, and the invention name is "dynamic library loading method, nuclear deployment adjustment method and related devices", The entire contents of which are incorporated herein by reference.

technical field

The present application relates to the field of computer technologies, and in particular, to a method for loading a dynamic library, a method for adjusting core deployment, and a related device.

Background technique

A multi-core processor can support multiple concurrent applications at the same time. As an example, the multi-core processor in the base station supports the LTE standard of 4G and the NR standard of 5G. There are 100 4G users distributed in 3 cells; there are 50 5G users distributed in 3 cells. Core 1, core 2, and core 3 of the processor are responsible for resource allocation for 4G users, and core 4 and core 5 of the processor are responsible for resource allocation for 5G users. In practical applications, with the flow of people or the popularization of 5G, the number of 4G users and 5G users may change. For example, the number of 4G users drops to 50, and the number of 5G users rises to 100. At this time, due to the surge in the number of 5G users, core 4 and core 5 are no longer enough to support all 5G users. For this reason, real-time and rapid adjustments to the core deployment of 4G LTE and 5G NR systems are required, such as adjusting core 3. Deployed to be responsible for resource allocation for 5G users. At this time, it involves switching the dynamic library related to the 4G application of the kernel 3 to the dynamic library related to the 5G application, which involves the loading and unloading of the dynamic library. In order to improve the user experience, taking dynamic library loading as an example, in the prior art, the relevant dynamic library may be pre-linked in the code compilation stage for relocation. This saves the time consumed by relocation when the dynamic library is loaded, and improves the loading speed of the dynamic library.

However, since the pre-linking process is carried out in the compilation phase, if the dynamic library version is updated on the platform that supports the running of business applications, the version of the executable file of the dynamic library obtained by pre-linking is not compatible with the actual latest dynamic library version of the platform. Problems that cause dynamic library loading to fail have occurred from time to time. How to ensure the successful loading of the dynamic library on the basis of improving the loading speed of the dynamic library has become an urgent technical problem to be solved in this field.

SUMMARY OF THE INVENTION

The present application provides a method for loading a dynamic library, a method for adjusting core deployment, and a related device, so as to improve the loading speed of the dynamic library when the core deployment is adjusted, and solve the problem that the dynamic library fails to be loaded.

The embodiment of the present application provides a dynamic library loading method, including:

When the first application is loaded in the target kernel, the executable files of all the dynamic libraries to be loaded corresponding to the target kernel are obtained from the file system; the executable files of all the dynamic libraries to be loaded include: the version associated with the first service dynamic library The executable file of the dynamic library and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest dynamic library version of the platform that supports the loading of the first application;

Pre-link the executable files of all the dynamic libraries to be loaded separately, obtain the pre-linked executable files of each dynamic library to be loaded in all the dynamic libraries to be loaded, and pre-link each dynamic library to be loaded. The executable file is stored in the file system;

Acquire the pre-linked executable file of each dynamic library to be loaded from the file system, and load the pre-linked executable file of each dynamic library to be loaded into the target kernel.

Optionally, before obtaining the executable files of all dynamic libraries to be loaded from the file system, the method further includes:

A dynamic library load request is received; the dynamic library load request indicates all dynamic libraries and target kernels to be loaded.

Optionally, when loading the pre-linked executable file of each dynamic library to be loaded into the target kernel of the processor, the method further includes:

The pre-linked executable file of each dynamic library to be loaded is stored in the memory space corresponding to the target kernel in the memory with the pre-arranged storage address.

Optionally, when prelinking the executable files of all the dynamic libraries to be loaded respectively, the method further includes:

According to the storage granularity of the memory and the segment size of the executable file of each dynamic library to be loaded, the storage address of the pre-linked executable file of each dynamic library to be loaded is arranged.

Optionally, according to the storage granularity of the memory and the segment size of the executable file of each dynamic library to be loaded, the storage address of the pre-linked executable file of each dynamic library to be loaded is arranged, specifically including:

According to the storage granularity of the memory and the segment size of the executable file of the dynamic library whose storage address is newly arranged, determine the remaining storage space of the executable file of the dynamic library whose storage address is newly arranged;

Determine the top n dynamic libraries whose storage addresses are not arranged in the loading order, and determine the segment size of the executable files of the n dynamic libraries whose storage addresses are not arranged; n is a positive integer;

A dynamic library that can be stored in the remaining storage space and the segment size of the executable file is closest to the remaining storage space is determined from the n dynamic libraries whose storage addresses are not arranged. The addresses are programmed into the address range of the remaining memory space.

Optionally, the segment size of the executable file of the dynamic library includes: the size of the code segment and the size of the data segment in the executable file of the dynamic library.

Optionally, the file system includes: at least one dynamic library version container;

At least one dynamic library version container includes: a dynamic library version first container; the dynamic library version first container includes executable files of all dynamic libraries related to loading of the first application; executable files of all dynamic libraries related to loading of the first application are included. The executable files include: executable files of all dynamic libraries to be loaded corresponding to the target kernel;

Obtain the executable files of all dynamic libraries to be loaded corresponding to the target kernel from the file system, including:

The executable files of all dynamic libraries to be loaded corresponding to the target kernel are obtained from the first container of the dynamic library version.

Optionally, the file system further includes: a dynamic library pre-linked version container corresponding to each dynamic library version container, including a dynamic library pre-linked version first container corresponding to the dynamic library version first container;

Store the pre-linked executable file of each dynamic library to be loaded into the file system, including:

Store the pre-linked executable file of each dynamic library to be loaded into the first container of the pre-linked version of the dynamic library;

Obtain the pre-linked executable file of each dynamic library to be loaded from the file system, including:

Obtain the pre-linked executable file of each dynamic library to be loaded from the first container of the dynamic library pre-linked version.

Optionally, it also includes: when loading the first application on the target kernel again, directly obtaining the pre-linked executable files of all the dynamic libraries to be loaded corresponding to the target kernel from the file system, and converting each of the dynamic libraries to be loaded. The pre-linked executable is loaded into the target kernel.

Embodiments of the present application also provide a method for adjusting core deployment, including:

Receive a core deployment adjustment request; the core deployment adjustment request indicates all dynamic libraries to be unloaded corresponding to the target kernel and all dynamic libraries to be loaded corresponding to the target kernel;

According to the core deployment adjustment request, all dynamic libraries to be unloaded are unloaded from the target kernel, and the pre-linked executable files of all dynamic libraries to be loaded are obtained from the file system, and all dynamic libraries to be loaded are pre-linked. The executable is loaded into the target kernel;

The pre-linked executable files of all the dynamic libraries to be loaded are obtained after pre-linking the executable files of all the dynamic libraries to be loaded; the executable files of all the dynamic libraries to be loaded include: the first service dynamic library version The executable file of the associated dynamic library and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest dynamic library version of the platform that supports the loading of the first application.

The embodiment of the present application also provides a dynamic library loading device, including:

The obtaining module is used to, when the first application is loaded in the target kernel, obtain the executable files of all dynamic libraries to be loaded corresponding to the target kernel from the file system; the executable files of all the dynamic libraries to be loaded include: the first service The executable file of the dynamic library associated with the dynamic library version and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest dynamic library version of the platform that supports the loading of the first application;

The pre-link module is used to pre-link the executable files of all the dynamic libraries to be loaded separately, obtain the pre-linked executable files of each dynamic library to be loaded in all the dynamic libraries to be loaded, and link each dynamic library to be loaded. The pre-linked executable file of the dynamic library is stored in the file system;

The loading module is used to obtain the pre-linked executable file of each dynamic library to be loaded from the file system, and load the pre-linked executable file of each dynamic library to be loaded into the target kernel.

Embodiments of the present application also provide an apparatus for adjusting nuclear deployment, including:

The receiving module is used to receive a core deployment adjustment request; the core deployment adjustment request indicates all dynamic libraries to be unloaded corresponding to the target kernel and all dynamic libraries to be loaded corresponding to the target kernel;

The deployment adjustment module is used to unload all the dynamic libraries to be unloaded from the target kernel according to the core deployment adjustment request, obtain the pre-linked executable files of all the dynamic libraries to be loaded from the file system, and load all the dynamic libraries to be loaded. The executable file pre-linked by the dynamic library is loaded into the target kernel;

As can be seen from the above technical solutions, the embodiments of the present application at least have the following advantages:

In the dynamic library loading method provided by the present application, when the first application is loaded in the target kernel, the executable files of all the dynamic libraries to be loaded corresponding to the target kernel are obtained from the file system; the executable files of all the dynamic libraries to be loaded include: : the executable file of the dynamic library associated with the first service dynamic library version and the executable file of the dynamic library associated with the first platform dynamic library version. The first platform dynamic library version is the latest dynamic library version of the platform that supports the loading of the first application. Pre-link the executable files of all the dynamic libraries to be loaded separately, obtain the pre-linked executable files of each dynamic library to be loaded in all the dynamic libraries to be loaded, and pre-link each dynamic library to be loaded. The executable file is stored in the file system; the pre-linked executable file of each dynamic library to be loaded is obtained from the file system, and the pre-linked executable file of each dynamic library to be loaded is loaded into the target kernel. In some scenarios, the application of the target kernel is usually switched frequently, for example, frequently switching from the second application to the first application, and frequently switching from the first application to the second application. In the technical solution of the present application, since the pre-linked executable file of each dynamic library to be loaded is stored in the file system, when the first application needs to be switched and loaded on the target kernel in the future, it can be directly The pre-linked executable files of these dynamic libraries to be loaded are obtained from the file system, without performing the pre-linking operation every time. In this way, the loading speed of the dynamic library is improved. In addition, since the first pre-linking is performed when the target kernel loads the first application, pre-linking can be performed based on the executable file of the dynamic library associated with the latest dynamic library version of the platform. In this way, the pre-linked executable file is compatible with the latest dynamic library version of the platform, avoiding the problem of dynamic library loading failure.

Description of drawings

1 is a schematic flowchart of a dynamic library loading method provided by an embodiment of the present application;

2 is a schematic diagram comparing the storage effects of executable files after dynamic library pre-linking before memory arrangement and after memory arrangement according to an embodiment of the present application;

3 is a schematic structural diagram of a file system according to an embodiment of the present application;

FIG. 4 is a schematic flowchart of a method for adjusting core deployment provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of an application scenario of a method for adjusting core deployment provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of another file system provided by an embodiment of the present application;

7A is a signaling diagram of a dynamic library loading method provided by an embodiment of the present application;

7B is a signaling diagram of a method for adjusting core deployment provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a dynamic library loading apparatus provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of an apparatus for adjusting core deployment according to an embodiment of the present application.

Detailed ways

Before introducing the embodiments of the present application, in order to better understand the solutions provided by the embodiments of the present application, several technical terms appearing in the present application are explained below.

Dynamic library: relocatable object files are packaged into a single file in a specific way, and when linking to generate an executable file, "copy" what it needs from this single file to the final executable file, and it is not necessary to "copy" all the binary code of the required content into the executable file at link time, but only "copy" some relocation and symbol table information, which can be completed when the program is running. the linking process. This separate file is called a dynamic library.

Global Offset Table (GOT) table: A table used to locate global variables and functions.

Pre-Link (Pre-Link): is a method to optimize application load time by resolving library symbols before startup.

As described above, the pre-linking process of the current dynamic library loading method is carried out in the compilation stage. If the version of the dynamic library is updated on the platform that supports the operation of the business application, the version of the executable file of the dynamic library obtained by the previous pre-linking will be the same as the actual version of the platform. The latest dynamic library version is not compatible, and the problem that the dynamic library loading fails sometimes occurs. At present, a technical solution of using GOT table to load dynamic library can also be adopted. In this scheme, all applications need to perform jump access through the GOT table, which increases the running consumption and thus affects the performance of the system.

In order to solve the above problems, the present application provides a dynamic library loading method, an adjustment method for core deployment, and a related device, which can ensure the successful loading of the dynamic library on the basis of improving the loading speed of the dynamic library. And compared with the GOT table loading dynamic library scheme, there will be no additional running consumption, so it will not have a negative impact on the performance of the system. In order to make the above objects, features and advantages of the present application more clearly understood, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings and specific implementation manners. Referring to FIG. 1 , this figure is a schematic flowchart of a dynamic library loading method provided by an embodiment of the present application. As shown in FIG. 1 , the dynamic library loading method provided by the embodiment of the present application includes the following steps S101 to S103:

S101: When the first application is loaded on the target kernel, obtain executable files of all dynamic libraries to be loaded corresponding to the target kernel from the file system; the executable files of all dynamic libraries to be loaded include: a first service dynamic library version The executable file of the associated dynamic library and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest dynamic library version of the platform that supports the loading of the first application.

In the implementation scenario of the technical solution of the present application, the dynamic library is loaded to at least one core of the multi-core processor. The target kernel is one of at least one kernel that needs to load dynamic libraries. There are various reasons for loading the dynamic library into the target kernel, and the reasons for loading are described below with examples.

An example reason is that the target kernel is idle, and other kernels loaded with the first application are insufficient to support the current traffic of the first application. The target kernel needs to be converted from an idle state to a working state supporting services related to the first application. For this purpose, a dynamic library related to the first application needs to be loaded into the target kernel.

Another example reason is that the target kernel has previously loaded relevant dynamic libraries of other applications, but due to the adjustment of the kernel deployment, the target kernel needs to be switched from other applications to the first application. For this purpose, a dynamic library related to the first application needs to be loaded into the target kernel.

The file system is a system outside the processor that stores all dynamic library-related files, independent of memory. Specifically, the file system may store the platform-related dynamic library and the file system of the service-related dynamic library. Among them, the business-related dynamic library is most closely related to the application switching of the target kernel. The platform specifically refers to a system that supports loading and running of the first application, for example, an operating system. Platform-related dynamic libraries may undergo version updates. Similarly, business-related dynamic libraries may also undergo version updates. The version updates of dynamic libraries are embodied in the file system.

In the technical solution of the present application, it is assumed that the target kernel needs to be switched to a working state that supports services related to the first application. To achieve this purpose, when loading the first application, the processor obtains executable files of all dynamic libraries to be loaded corresponding to the target kernel from the file system. Wherein, it includes both the executable file of the dynamic library associated with the first service dynamic library version, and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version supports the loading of the first application The latest dynamic library version for the platform.

The first service dynamic library version refers to a dynamic library version formed by a collection of executable files of all service-related dynamic libraries to be loaded in order to load the first application. The first platform dynamic library version refers to a dynamic library version formed by a collection of executable files of all the latest platform-related dynamic libraries in order to load the first application.

It should be noted that if the application to be loaded changes, for example, switching from the first application to loading the second application, the executable files of all dynamic libraries to be loaded corresponding to the target kernel may change. Among them, business-related dynamic libraries may change; platform-related dynamic libraries may change or remain unchanged. As an example, all the executable files of the dynamic library to be loaded include: the executable file of the dynamic library associated with the second service dynamic library version and the executable file of the dynamic library associated with the second platform dynamic library version. The second service dynamic library version refers to a dynamic library version formed by a collection of executable files of all service-related dynamic libraries to be loaded in order to load the second application. The second platform dynamic library version refers to a dynamic library version formed by a collection of executable files of all the latest platform-related dynamic libraries in order to load the second application.

In some embodiments, the dynamic library associated with the first service dynamic library version and the dynamic library associated with the second service dynamic library version may be partially the same, or may be completely different.

S102: Pre-link the executable files of all the dynamic libraries to be loaded respectively, obtain the pre-linked executable files of each dynamic library to be loaded in all the dynamic libraries to be loaded, and pre-link each dynamic library to be loaded. The linked executable is stored in the file system.

Pre-linking an executable file of a dynamic library is a relatively mature technology in the art, so the implementation manner of pre-linking is not limited here, and the implementation process of pre-linking is not described in detail. Different from the occurrence period (in the compilation stage) of the existing pre-link technology, in the embodiment of the present application, the occurrence period of the pre-link technology is implemented in the first application loading process. During the loading process of the first application, even if the dynamic library version associated with the platform is adjusted and updated in real time, it can respond in time, avoiding the problem of incompatibility with the platform version after pre-linking.

S103: Acquire the pre-linked executable file of each dynamic library to be loaded from the file system, and load the pre-linked executable file of each dynamic library to be loaded into the target kernel.

As an example, in step S101, the executable files of all dynamic libraries to be loaded corresponding to the target kernel are obtained from the file system, including the executable files of the dynamic libraries p1, p2 and p3 and the executable files of the dynamic libraries s1, s2, s3 and s4. The execution file, wherein the dynamic libraries p1-p3 are dynamic libraries associated with the first service dynamic library version, and the dynamic libraries s1-s4 are dynamic libraries associated with the first platform dynamic library version. Step S101 pre-links the executable files of the dynamic libraries p1-p3 and s1-s4 respectively, and imports the pre-linked executable files of the dynamic libraries p1-p3 and s1-s4 into the file system. In this step S103, in order to load these dynamic libraries, the pre-linked executable files of the dynamic libraries p1-p3 and s1-s4 are taken out from the file system and loaded into the target kernel. The above-mentioned p1-p3 and s1-s4 are not shown in the figure.

As can be seen from the above, in the dynamic library loading method provided by the embodiments of the present application, the executable file of the dynamic library to be loaded is pre-linked, and the pre-linked executable file is stored in the file system, so as to facilitate the retrieval again, Improved the loading speed of dynamic libraries. In addition, since the first pre-linking is performed when the target kernel loads the first application, pre-linking can be performed based on the executable file of the dynamic library associated with the dynamic library version of the platform at that time, so that the pre-linked platform dynamic library can be pre-linked. The version is the latest. In this way, the problem that the pre-linked executable file does not match the latest dynamic library version of the platform is avoided, and the compatibility performance is guaranteed.

In this embodiment of the present application, before obtaining the executable files of all dynamic libraries to be loaded from the file system, a dynamic library loading request may also be received; the dynamic library loading request indicates all the dynamic libraries to be loaded and the target kernel. It should be noted that, in this embodiment of the present application, the information of all dynamic libraries to be loaded and the target kernel can be directly obtained according to the dynamic library loading request itself, or all the dynamic libraries to be loaded and the target kernel can be indicated according to the dynamic library loading request. The ID information of the target kernel obtains all dynamic libraries to be loaded and the target kernel, which is not limited in this embodiment of the present application. As an example: the method provided by the embodiment of the present application can obtain the dynamic library to be loaded as dynamic library A according to the ID information 001 in the dynamic library loading request and the mapping relationship between the ID information and the dynamic library, according to the ID information 002 and the ID information and the dynamic library A From the mapping relationship of the dynamic library, the dynamic library to be loaded can be obtained as dynamic library B.

To load the pre-linked executable file of the dynamic library into memory, the requested storage granularity is a fixed value. For example: when the storage granularity of the application is 4k, the storage granularity of each application is an integer multiple of 4k. The order of loading the dynamic library is certain. After the action of loading the pre-linked executable files of the dynamic library in sequence is completed, there may be a large hole in the memory, so that the executable file after the dynamic library pre-linking is loaded as a whole. Occupy a lot of memory, or the problem of wasting memory space.

Because the method provided by the embodiment of the present application is to pre-link all executable files to be loaded, the storage addresses of these files in the memory can be arranged based on these linked executable files, so as to reduce the memory usage. Empty. In the method provided by this embodiment of the present application, when pre-linking the executable files of all dynamic libraries to be loaded respectively, according to the storage granularity of the memory and the segment size of the executable files of each dynamic library to be loaded, The storage address of the pre-linked executable file of each dynamic library to be loaded is arranged. Here, the storage addresses are arranged according to the segment size of the executable file of each dynamic library to be loaded because the corresponding segment size does not change significantly before and after pre-linking. In this embodiment of the present application, the segment size of the executable file of the dynamic library specifically includes: the size of the code segment and the size of the data segment. Code segments and data segments have different properties. It should be noted that the essence of an executable file is a description file, and the size of the executable file itself does not represent the size of the memory occupied by the executable file after it is loaded into the memory. The format of the executable file can be ELF (Executable and Linkable Format) format.

When organizing memory, memory can be organized separately based on different attributes. For example, according to the size of the data segment in the executable file of the dynamic library 1 to be loaded and the size of the data segment in the executable file of the dynamic library 2 to be loaded, the memory arrangement is unified; according to the executable file of the dynamic library 1 to be loaded The size of the code segment and the size of the code segment in the executable file of the dynamic library 2 to be loaded are unified for memory arrangement.

In order to demonstrate the technical effect of memory arrangement in the technical solution of the present application, firstly, Fig. 2 shows the storage effect of a pre-linked executable file of a dynamic library before memory arrangement (see section 2a) and the memory arrangement according to the technical solution of the present application. The storage effect of the pre-linked executable after the orchestration dynamic library (see section 2b). In this example, the loading order of the dynamic library is predetermined, and it is necessary to load the dynamic library 0, the dynamic library 1, the dynamic library 2, and the dynamic library 3 in sequence. First, introduce part 2a in Figure 2. When dynamic library 2 is loaded into memory as shown in part 2a of Figure 2, the remaining storage space of dynamic library 0 is larger than the pre-linked executable file of dynamic library 2. segment size, then dynamic library 2 will be stored in the remaining storage space of dynamic library 0; when loading dynamic library 3, since the remaining space of dynamic libraries 0 to 2 is smaller than the segment size of the executable file pre-linked by dynamic library 3, Then the dynamic library 3 will re-apply for a granular memory to store in it. Since part 2b shows the technical effects of the technical solutions of the present application, the following will first introduce the technical solutions provided by the implementation of the present application and examples of application of the technical solutions.

In this embodiment of the present application, the storage address of the pre-linked executable file of each dynamic library to be loaded may be stored according to the storage granularity of the memory and the segment size of the pre-linked executable file of each dynamic library to be loaded. Make arrangements. An example implementation is provided below. It should be understood that the following examples do not constitute a limitation on the methods provided in the present application.

As a possible implementation manner, according to the storage granularity of the memory and the segment size of the executable file of each dynamic library to be loaded, the storage address of the executable file after pre-linking of each dynamic library to be loaded is arranged, Can specifically include:

According to the storage granularity of the memory and the segment size of the executable file of the dynamic library whose storage address is newly arranged, determine the remaining storage space of the executable file of the dynamic library whose storage address is newly arranged; The dynamic library whose address is not arranged, and determine the segment size of the executable file of n storage addresses of the dynamic library whose address is not arranged; n is a positive integer (for example, n is 3, n is not limited here, and n can also be all remaining The total number of dynamic libraries with unprogrammed storage addresses); determine a dynamic library that can be stored in the remaining storage space and the segment size of the executable file is the closest to the remaining storage space from the n dynamic libraries with unprogrammed storage addresses. The storage address of the executable file pre-linked by the dynamic library is programmed into the address range of the remaining storage space. If the smallest segment size of the executable files of the dynamic library whose storage addresses are not arranged cannot be stored in the remaining storage space, the storage granularity can be re-applied, or the value of n can be enlarged. In this way, it can be ensured that the remaining space in each granular memory can be used to the greatest extent possible, so that the memory occupied by the pre-linked executable files of all the dynamic libraries to be loaded can be reduced, and the dynamic libraries can be loaded and unloaded from the memory. speed increased.

Referring to FIG. 2 , part 2b in FIG. 2 is a schematic diagram of the storage effect of the pre-linked executable file of the arranged dynamic library in the memory. The memory shown in part 2b arranges the storage address of each pre-linked executable file of the dynamic library to be loaded according to the storage granularity of the memory before loading, and then loads the pre-linked executable file of the dynamic library according to the arrangement result. . Since the segment size of the executable file of dynamic library 3 is larger than the segment size of the executable file of dynamic library 2, the segment size of the executable file of dynamic library 1 is relatively too large, and the remaining storage space corresponding to dynamic library 0 is larger than The segment size of the executable file of the dynamic library 3, so in order to more fully utilize the remaining space corresponding to the dynamic library 0, the dynamic library 3 is loaded into the remaining space corresponding to the dynamic library 0 during the programming process.

Dynamic libraries

1 and 2 will be loaded into the granular memory of the newly allocated memory. It can be seen from the above that the dynamic library 3 is loaded into the newly applied granular memory before the arrangement, and the dynamic library 3 is loaded into the remaining space corresponding to the dynamic library 0 after the arrangement. As shown in FIG. 2 , the segment size of dynamic library 3 is larger than that of dynamic library 2. Therefore, on the whole, dynamic library 0, dynamic library 1, dynamic library 2, and dynamic library 3 occupy less memory.

In the above technical solution, since the executable files of all the dynamic libraries to be loaded are pre-linked uniformly (for example, pre-linked in the same period of time), rather than pre-linked in different periods of time again and again, the above-mentioned arrangement operation for memory is made. become possible.

In order to utilize the requested memory as much as possible, save memory consumption, and improve the speed of loading and unloading dynamic libraries, as a possible implementation manner, in this embodiment of the present application, each dynamic library to be loaded is pre- When the linked executable file is loaded into the target kernel of the processor, the method provided by the embodiment of the present application may further include: storing the pre-linked executable file of each dynamic library to be loaded into a pre-arranged storage address. into the storage space corresponding to the target kernel in memory.

It can be seen from the above that the method provided by the embodiment of the present application arranges the storage address of the pre-linked executable file of each dynamic library to be loaded according to the storage granularity of the memory and the segment size of the executable file, which reduces the size of the executable file. The memory hole when the execution file is stored in the memory can reduce the memory occupied by the pre-linked executable file, improve the memory performance, and improve the speed of loading and unloading the dynamic library in the memory.

The file system in the embodiment of the present application is described in detail below:

The file system provided by the embodiment of the present application includes: at least one dynamic library version container;

Specifically, the at least one dynamic library version container includes: a first dynamic library version container; the first dynamic library version container includes executable files of all dynamic libraries related to loading the first application; all dynamic library versions related to loading the first application The executable files of the library include: executable files of all dynamic libraries to be loaded corresponding to the target kernel. Therefore, in the embodiment of the present application, obtaining executable files of all dynamic libraries to be loaded corresponding to the target kernel from the file system specifically includes: obtaining all the dynamic libraries to be loaded corresponding to the target kernel from the first container of the dynamic library version executable file. The file system provided by the embodiment of the present application further includes: a dynamic library pre-linked version container corresponding to each dynamic library version container, including a dynamic library pre-linked version first container corresponding to the dynamic library version first container. Therefore, in the implementation of the present application, storing the pre-linked executable file of each dynamic library to be loaded into the file system specifically includes: storing the pre-linked executable file of each dynamic library to be loaded into the dynamic library Pre-linked version of the first container. In the embodiment of the present application, acquiring the pre-linked executable file of each dynamic library to be loaded from the file system specifically includes: acquiring the pre-linked executable file of each dynamic library to be loaded from the first container of the pre-linked version of the dynamic library executable file.

As an example, refer to FIG. 3 , which is a schematic structural diagram of a file system provided by an embodiment of the present application.

As shown in FIG. 3 , after the loading module 100 in the digital signal processor 1000 (Digital Signal Processor, DSP) obtains the dynamic library loading request, the loading module 100 obtains all the pending files corresponding to the target kernel from the first container 300 of the dynamic library version. Loaded dynamic library executable. Then, the loading module 100 stores the pre-linked executable file of each dynamic library to be loaded into the first container 400 of the pre-linked version of the dynamic library. The loading module 100 in the DSP processor 1000 obtains the pre-linked executable file of each dynamic library to be loaded from the first container 400 of the dynamic library pre-linked version. In addition, correspondingly, loading the pre-linked executable file of each dynamic library to be loaded into the target kernel in this application may further include: the loading module 100 in the DSP processor 1000 pre-loads each dynamic library to be loaded. The linked executable is loaded into the target kernel.

In practical applications, when the pre-linked executable file is loaded into the target kernel, it may be necessary to load the previously loaded executable file again. At this time, if each dynamic library to be loaded is re-linked Converting it into an executable file will cost a lot of computing resources. Therefore, when the pre-linked executable file of each dynamic library to be loaded is loaded into the target kernel of the processor, the method provided by this embodiment of the present application may further include: when the first application is loaded on the target kernel again, All pre-linked executable files of the dynamic library to be loaded corresponding to the target kernel are directly obtained from the file system, and each pre-linked executable file of the dynamic library to be loaded is loaded into the target kernel. It can be seen from the above that in the method provided by the embodiment of the present application, by storing the pre-linked executable file of each dynamic library to be loaded into the file system, when the executable file that has been loaded needs to be loaded again, it can be loaded from the file system. It is directly loaded in the file system, thus eliminating the need to link each dynamic library to be loaded into an executable file again, saving computing resources, and at the same time improving the speed of loading dynamic libraries when the target kernel application is switched.

According to the above-mentioned method for loading a dynamic library, an embodiment of the present application further provides a method for adjusting core deployment.

Referring to FIG. 4 , this figure is a schematic flowchart of a method for adjusting core deployment provided by an embodiment of the present application. As shown in FIG. 4 , the method for adjusting core deployment provided by this embodiment of the present application includes the following steps S401 to S403:

S401: Receive a core deployment adjustment request; the core deployment adjustment request indicates all dynamic libraries to be unloaded corresponding to the target kernel and all dynamic libraries to be loaded corresponding to the target kernel.

S402: Unload all dynamic libraries to be unloaded from the target kernel according to the core deployment adjustment request, obtain pre-linked executable files of all dynamic libraries to be loaded from the file system, and pre-link all dynamic libraries to be loaded After the executable is loaded into the target kernel.

In the embodiment of the present application, the pre-linked executable files of all the dynamic libraries to be loaded are obtained after pre-linking the executable files of all the dynamic libraries to be loaded; the executable files of all the dynamic libraries to be loaded include : the executable file of the dynamic library associated with the first service dynamic library version and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest update of the platform that supports the loading of the first application library version.

Next, a specific example will be used to introduce the method for adjusting core deployment provided by the embodiment of the present application. Referring to FIG. 5 , this figure is a schematic diagram of an application scenario of the method for adjusting core deployment provided by the embodiment of the present application.

As shown in FIG. 5 , the core deployment adjustment method provided by the present application can redeploy the core 3 in the processor 5 cores in the figure, and the core 3 is used as an example to illustrate: Specifically, the method provided by the present application will , application) 0 is unloaded from the core 3, and obtains all pre-linked executable files related to APP1 to be loaded from the file system, and loads all the pre-linked executable files related to APP1 to be loaded into the core 3. In this way, the core 3 originally deployed in APP0 can be deployed to APP1. Correspondingly, the method provided by the present application can also unload all pre-linked executable files related to APP1 to be loaded from core 3, and obtain all pre-linked executable files related to APP0 to be loaded from the file system. file, load all pre-linked executable files related to APP0 to be loaded into core 3, so that core 3 originally deployed in APP1 can be deployed to APP0. It can be understood that the cores deployed by the methods provided in the embodiments of the present application are not limited to the core 3 in the above example, but include any one or more deployable cores. Meanwhile, the platform and application in this application do not limit the dynamic library for core deployment adjustment. As an example, the method for core deployment provided by the present application can also be applied to the readjustment and deployment of the core deployed in the 4G service and the core deployed in the 5G service in the signal base station.

Referring to FIG. 6 , this figure is a schematic structural diagram of another file system provided by an embodiment of the present application. As shown in FIG. 6 , after the deployment adjustment module 200 in the DSP 1000 receives the core deployment adjustment request, the deployment adjustment module 200 unloads all the dynamic libraries to be uninstalled from the target kernel according to the core deployment adjustment request, and pre-links the version from the dynamic library The first container 400 obtains all pre-linked executable files of the dynamic library to be loaded, and loads all the pre-linked executable files of the dynamic library to be loaded into the target kernel.

In order to more intuitively show the dynamic library loading method and the core deployment adjustment method provided by the embodiments of the present application, the above methods are shown in the form of a signaling diagram next.

Referring to FIG. 7A , this figure is a signaling diagram of a dynamic library loading method provided by an embodiment of the present application.

As shown in FIG. 7A , after the loading of the loading module is triggered externally, the loading module obtains the versions of all dynamic libraries through the first container of the dynamic library version; the loading module pre-links all the dynamic libraries together, and pre-links the The version is sent to the first container of the dynamic library pre-linked version for storage. Then, the loading module obtains the pre-linked version of the dynamic library stored in the first container from the pre-linked version of the dynamic library (including all pre-linked executable files of the dynamic library to be loaded), and loads the pre-linked version of the dynamic library. version of the executable is loaded onto the target kernel.

Referring to FIG. 7B , this figure is a signaling diagram of a method for adjusting core deployment provided by an embodiment of the present application.

As shown in FIG. 7B , after the adjustment of the deployment adjustment module is triggered externally, the deployment adjustment module will unload the dynamic library on the corresponding target kernel, and obtain the pre-linked version of the dynamic library from the first container of the pre-linked version of the dynamic library , and load the executable file of the pre-linked version of the dynamic library into the target kernel.

For example, the unloaded dynamic library is a dynamic library associated with other applications other than the first application. Here, when the kernel needs to be switched from another application to the first application, the dynamic library associated with the other application can be unloaded, and then loaded again. The executable file after all dynamic libraries related to the first application are pre-linked.

It should be noted that, the APP in the embodiment of the present application may be an application program on a terminal, and may also be an application under different standards. For example, APP0 can be an application of 4G LTE standard, and APP1 can be an application of 5G NR standard. The form of application is not limited here.

It can be seen from the above that the method provided by the embodiments of the present application pre-links the executable file of the dynamic library to be loaded, and stores the pre-linked executable file in the file system, so as to facilitate the retrieval again and improve the dynamic performance. The loading speed of the library also avoids the problem that the pre-linked executable file does not match the latest dynamic library version of the platform. Further, the method provided by the embodiment of the present application also arranges the storage address of the executable file according to the storage granularity of the memory and the segment size of the executable file, so that the memory occupied by the pre-linked executable file can be reduced. , memory performance improvement, memory loading dynamic library and unloading dynamic library speed increase.

According to the dynamic library loading method provided by the above method embodiments, an embodiment of the present application further provides a dynamic library loading apparatus. Referring to FIG. 8 , this figure is a schematic structural diagram of a dynamic library loading apparatus provided by an embodiment of the present application. As shown in FIG. 8 , the dynamic library loading device provided by the embodiment of the present application includes:

The obtaining module 801 is used to, when the first application is loaded in the target kernel, obtain from the file system the executable files of all the dynamic libraries to be loaded corresponding to the target kernel; the executable files of all the dynamic libraries to be loaded include: the first The executable file of the dynamic library associated with the service dynamic library version and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest dynamic library version of the platform that supports the loading of the first application;

The pre-linking module 802 is used to pre-link the executable files of all the dynamic libraries to be loaded respectively, obtain the pre-linked executable files of each dynamic library to be loaded in all the dynamic libraries to be loaded, and link each dynamic library to be loaded. The pre-linked executable file of the loaded dynamic library is stored in the file system;

The loading module 803 is used to obtain the pre-linked executable file of each dynamic library to be loaded from the file system, and load the pre-linked executable file of each dynamic library to be loaded into the target kernel.

As a possible implementation manner, before obtaining the executable files of all the dynamic libraries to be loaded from the file system, the dynamic library loading apparatus provided in this embodiment of the present application further includes: a receiving module configured to receive a dynamic library loading request; The dynamic library load request indicates all dynamic libraries and target kernels to be loaded.

As a possible implementation manner, the loading module 803 is further configured to: store the pre-linked executable file of each dynamic library to be loaded into the storage space corresponding to the target kernel in the memory with a pre-programmed storage address.

As a possible implementation manner, when all executable files of the dynamic library to be loaded are pre-linked, the dynamic library loading apparatus provided in this embodiment of the present application further includes: an orchestration module for, according to the storage granularity of the memory and each The segment size of the executable file of each dynamic library to be loaded is arranged, and the storage address of the pre-linked executable file of each dynamic library to be loaded is arranged.

As a possible implementation manner, the orchestration module is specifically configured to: determine, according to the storage granularity of the memory and the segment size of the executable file of the dynamic library whose storage address is newly arranged Remaining storage space; determine the dynamic libraries with the unarranged n storage addresses at the top of the loading order, and determine the segment size of the executable file of the dynamic libraries with n storage addresses unarranged; n is a positive integer; from n storage addresses A dynamic library that can be stored in the remaining storage space and the segment size of the executable file is closest to the remaining storage space is determined from the unprogrammed dynamic library, and the storage address of the executable file pre-linked to the dynamic library is arranged to the remaining storage space. within the address range of the space.

As a possible implementation manner, the dynamic library loading apparatus provided in the embodiment of the present application further includes: a direct acquisition module for directly acquiring all pending files corresponding to the target kernel from the file system when the first application is loaded on the target kernel again. Loading the pre-linked executable file of the loaded dynamic library, and loading the pre-linked executable file of each dynamic library to be loaded into the target kernel.

According to the method for adjusting nuclear deployment provided by the above method embodiments, an embodiment of the present application further provides an apparatus for adjusting nuclear deployment. Referring to FIG. 9 , this figure is a schematic structural diagram of an apparatus for adjusting core deployment provided by an embodiment of the present application. As shown in FIG. 9 , the apparatus for adjusting core deployment provided by the embodiment of the present application includes:

The receiving module 901 is configured to receive a core deployment adjustment request; the core deployment adjustment request indicates all dynamic libraries to be unloaded corresponding to the target kernel and all dynamic libraries to be loaded corresponding to the target kernel;

The deployment adjustment module 902 is configured to, according to the core deployment adjustment request, unload all the dynamic libraries to be unloaded from the target kernel, obtain the pre-linked executable files of all the dynamic libraries to be loaded from the file system, and load all the dynamic libraries to be loaded. The pre-linked executable file of the dynamic library is loaded into the target kernel;

The method for loading a dynamic library, the method for adjusting core deployment, and the related apparatus provided in the above solution can be specifically applied to a multi-core processor.

The above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The recorded technical solutions are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

A method for loading a dynamic library, comprising:

When the first application is loaded in the target kernel, the executable files of all the dynamic libraries to be loaded corresponding to the target kernel are obtained from the file system; the executable files of all the dynamic libraries to be loaded include: the first service dynamic The executable file of the dynamic library associated with the library version and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest dynamic library supporting the platform loaded by the first application Version;

Prelink the executable files of all the dynamic libraries to be loaded respectively, obtain the prelinked executable files of each dynamic library to be loaded in all the dynamic libraries to be loaded, and link each dynamic library to be loaded. The executable file after library pre-linking is stored in the file system;

Acquire a pre-linked executable file of each dynamic library to be loaded from the file system, and load the pre-linked executable file of each dynamic library to be loaded into the target kernel.
The method for loading a dynamic library according to claim 1, characterized in that before obtaining the executable files of all dynamic libraries to be loaded from the file system, the method further comprises:

A dynamic library loading request is received; the dynamic library loading request indicates all dynamic libraries to be loaded and the target kernel.
The dynamic library loading method according to claim 1, wherein when the pre-linked executable file of each dynamic library to be loaded is loaded into the target kernel of the processor, the method further comprises:

The pre-linked executable file of each dynamic library to be loaded is stored in the memory space corresponding to the target kernel in the memory with the pre-arranged storage address.
The dynamic library loading method according to claim 3, wherein when the executable files of all the dynamic libraries to be loaded are pre-linked respectively, the method further comprises:

According to the storage granularity of the memory and the segment size of the executable file of each dynamic library to be loaded, the storage address of the pre-linked executable file of each dynamic library to be loaded is arranged.
The method for loading a dynamic library according to claim 4, wherein, according to the storage granularity of the memory and the segment size of the executable file of each dynamic library to be loaded, each dynamic library to be loaded is pre-loaded. The storage address of the linked executable file is arranged, including:

According to the storage granularity of the memory and the segment size of the executable file of the dynamic library whose storage addresses are newly arranged, determine the remaining storage space of the executable file of the dynamic library whose storage addresses are newly arranged;

Determine the dynamic libraries whose loading order is not arranged in the top n storage addresses, and determine the segment size of the executable files of the dynamic libraries whose storage addresses are not arranged; the n is a positive integer;

A dynamic library that can be stored in the remaining storage space and the segment size of the executable file is closest to the remaining storage space is determined from the n dynamic libraries whose storage addresses are not arranged, and the dynamic library is pre-linked after the The storage address of the executable file is programmed into the address range of the remaining storage space.
The method for loading a dynamic library according to claim 3 or 4, wherein the segment size of the executable file of the dynamic library includes: the size of the code segment and the size of the data segment in the executable file of the dynamic library.
The dynamic library loading method according to any one of claims 1-5, wherein the file system comprises: at least one dynamic library version container;

The at least one dynamic library version container includes: a first container for a dynamic library version; the first container for a dynamic library version includes executable files of all dynamic libraries related to loading of the first application; An executable file of all dynamic libraries related to application loading includes: executable files of all dynamic libraries to be loaded corresponding to the target kernel;

The executable files of all to-be-loaded dynamic libraries corresponding to the target kernel obtained from the file system specifically include:

The executable files of all dynamic libraries to be loaded corresponding to the target kernel are obtained from the first container of the dynamic library version.
The dynamic library loading method according to claim 7, wherein the file system further comprises: a dynamic library pre-linked version container corresponding to each dynamic library version container, including a first container corresponding to the dynamic library version The first container of the corresponding dynamic library pre-linked version;

The storing of the pre-linked executable file of each dynamic library to be loaded into the file system specifically includes:

storing the pre-linked executable file of each dynamic library to be loaded into the first container of the pre-linked version of the dynamic library;

The obtaining of the pre-linked executable file of each dynamic library to be loaded from the file system specifically includes:

The pre-linked executable file of each dynamic library to be loaded is obtained from the first container of the dynamic library pre-linked version.
The dynamic library loading method according to any one of claims 1-5, further comprising: when the first application is loaded on the target kernel again, directly acquiring the target kernel from the file system Corresponding to the pre-linked executable files of all the dynamic libraries to be loaded, the pre-linked executable files of each of the dynamic libraries to be loaded are loaded into the target kernel.
A method for adjusting nuclear deployment, comprising:

receiving a core deployment adjustment request; the core deployment adjustment request indicates all dynamic libraries to be unloaded corresponding to the target kernel and all dynamic libraries to be loaded corresponding to the target kernel;

According to the core deployment adjustment request, all the dynamic libraries to be unloaded are unloaded from the target kernel, and the pre-linked executable files of all the dynamic libraries to be loaded are obtained from the file system, and the All pre-linked executable files of the dynamic library to be loaded are loaded into the target kernel;

The pre-linked executable files of all the dynamic libraries to be loaded are obtained after pre-linking the executable files of all the dynamic libraries to be loaded; the executable files of all the dynamic libraries to be loaded include: the first The executable file of the dynamic library associated with the service dynamic library version and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest version of the platform that supports the loading of the first application Dynamic library version.
A dynamic library loading device, comprising:

The obtaining module is used to, when the first application is loaded in the target kernel, obtain the executable files of all the dynamic libraries to be loaded corresponding to the target kernel from the file system; the executable files of all the dynamic libraries to be loaded include: : the executable file of the dynamic library associated with the first service dynamic library version and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the one that supports the loading of the first application The latest dynamic library version of the platform;

The pre-linking module is used to pre-link the executable files of all the dynamic libraries to be loaded, respectively, to obtain the pre-linked executable files of each dynamic library to be loaded in all the dynamic libraries to be loaded, and to The pre-linked executable file of each dynamic library to be loaded is stored in the file system;

The loading module is used to obtain the pre-linked executable file of each dynamic library to be loaded from the file system, and load the pre-linked executable file of each dynamic library to be loaded into the target kernel.
An adjustment device for nuclear deployment, comprising:

The receiving module is configured to receive a core deployment adjustment request; the core deployment adjustment request indicates all dynamic libraries to be unloaded corresponding to the target kernel and all dynamic libraries to be loaded corresponding to the target kernel;

The deployment adjustment module is configured to, according to the core deployment adjustment request, unload all the dynamic libraries to be unloaded from the target kernel, and obtain the pre-linked executables of all the dynamic libraries to be loaded from the file system. an executable file, which loads the pre-linked executable files of all the dynamic libraries to be loaded into the target kernel;

The pre-linked executable files of all the dynamic libraries to be loaded are obtained after pre-linking the executable files of all the dynamic libraries to be loaded; the executable files of all the dynamic libraries to be loaded include: the first The executable file of the dynamic library associated with the service dynamic library version and the executable file of the dynamic library associated with the first platform dynamic library version, wherein the first platform dynamic library version is the latest version of the platform that supports the loading of the first application Dynamic library version.