TWI408605B - Method for executing process in user space and computer system using the same and recording medium - Google Patents

Abstract

A method for executing a program in a user space and a computer system using the same and a recording medium are provided. The user space includes a first program and a second program compiled from different compilers. The first program communicates with the second program through a filesystem module provided from a kernel so as to link to a third party library through the second program. Herein, the second program registers a virtual filesystem for the filesystem module through a filesystem library so that make the first program send an operation request to the second program through the virtual filesystem. The second program connects to the third party library according to the operation request for executing corresponding function of the third party library. Afterwards, the second program sends a response to the first program through the virtual filesystem.

Description

Execute user space program method, use its computer system and record media

The present invention relates to a method for using a user space program, and more particularly to a method for executing a user space program that can be linked to a library compiled by different compilers, a computer system using the same, and a recording medium.

In computer science, a library is a collection of subroutines used to develop software. A library is a code that provides services to other programs, not a stand-alone program. A library link refers to the inclusion of one or more libraries into a program. The dynamic libraries compiled by different compilers cannot be directly linked in programs compiled by different compilers because of different addressing methods.

For example, the general compiler for the Linux kernel is the GNU Compiler Collection (GNU Compiler Collection, under the GCC compiler) and GNU's GLIBC loader. The Android system is a software platform and operating system based on the Linux kernel. It uses the self-developed BIONIC compiler and BIONIC loader. The loader compiled by the BIONIC compiler cannot update the dynamic library memory address compiled by the GCC compiler at load time. As a result, the original Linux dynamic library cannot be linked. All programs must be re-enabled by the BIONIC compiler. Compile to properly link. But without the source code, the BIONIC compiler cannot be recompiled.

The present invention provides a method for executing a user space program and a computer system using the same, and can link a library compiled by different compilers without recompiling.

In particular, the present invention provides a method of executing a user space program suitable for use in a computer system. The computer system includes a user space and a core, and the user space includes a first program, wherein the first program is linked to the first standard library, and the first program and the first standard library are compiled by the first compiler. Here, a second program and a third-party library are provided in the user space, wherein the second program is linked to the second standard library, and the second program and the second standard library are compiled by the second compiler. The third-party library depends on the second standard library. The first program communicates with the second program through the file system module provided by the core to connect to the third-party library through the second program. The file system module has a corresponding file system library in the user space. The step of linking the first program to the third-party library through the second program includes: the second program registers the virtual file system with the file system module through the file system library; the first program transmits the operation request to the first file through the virtual file system. The second program is linked to the third-party library according to the operation request to execute the corresponding function in the third-party library; the second program transmits the response to the first program through the virtual file system.

In an embodiment of the present invention, the step of registering the virtual file system with the file system module through the file system library includes: the second program calls the registration function of the file system library to transmit the file system The path and the function indicator of the second standard library; the registration function transmits the open request to the core through the open function of the second standard library; the core opens the virtual device according to the open request, so that the virtual device transmits the operation descriptor to The second program; the second program transmits a setup request to the core through the control function of the second standard library to establish a virtual file system according to the file system path.

In an embodiment of the present invention, after the step of registering the virtual file system with the file system module by the second program through the file system library, the second program calls the wait function of the file system library to turn Ask the virtual file system whether it receives an operation request.

In an embodiment of the present invention, before the second program is linked to the third-party library according to the operation request, before the step of executing the corresponding function in the third-party library, if the waiting program polls the virtual file system When an operation request is received, the processing function of the file system library is called to parse the operation request.

In an embodiment of the present invention, the step of transmitting, by the first program, the operation request to the second program through the virtual file system comprises: the first program calling the function of the first standard library to transmit the operation request to the virtual file system to The file system module, wherein the operation request includes a file system path; the file system module transmits the operation request to the second program according to the file system path.

In an embodiment of the invention, the file system module is a file system in user space (FUSE) module. In addition, the format of the operation request is Extensible Markup Language (XML).

Additionally, the present invention provides a computer system including a core and user space. The core provides a file system module. The user space includes a file system library corresponding to the file system module, a first program, a first standard library, a second program, a second standard library, and a third-party library. Wherein, the first program is linked to the first standard library, which is compiled by the first compiler; and the second program is linked to the second standard library, which is compiled by the second compiler; The library is dependent on the second standard library. The second program registers the virtual file system with the file system module through the file system library, so that the first program can transmit the operation request to the second program through the virtual file system. The second program is linked to the third-party library according to the operation request, so as to execute the corresponding function in the third-party library. After that, the second program transmits a response to the first program through the virtual file system.

The invention further provides a computer readable recording medium for storing a user space program and for loading into a computer system for execution. The user space program includes a first program and a second program, and the computer system includes a user space and a core. The user space includes a first program, wherein the first program is linked to the first standard library, and the first program and the first standard library are compiled by the first compiler. The method for executing the user space program includes: providing a second program and a third-party library in the user space, wherein the second program is linked to the second standard library, and the second program and the second standard library are Compiled by the second compiler, and the third-party library is dependent on the second standard library. The first program will communicate with the second program through the file system module provided by the core to connect to the third-party library through the second program. The file system module has a corresponding file system library in the user space. . The step of linking the first program to the third-party library through the second program includes: the second program registers the virtual file system with the file system module through the file system library; the first program transmits the operation request to the first file through the virtual file system. The second program is linked to the third-party library according to the operation request to execute the corresponding function in the third-party library; the second program transmits a response to the first program through the virtual file system.

Based on the above, the file system module provided by the core enables the first program compiled by different compilers in the user space to communicate with the second program, and then uses the communication mode to cause the first program to call the second program. And through the second program to link to the third-party library. Accordingly, without recompiling the third-party library, the first program can call the third-party library through the help of the second program.

The above described features and advantages of the present invention will be more apparent from the following description.

The libraries compiled by different compilers have different addressing methods. Therefore, if the program compiled by the first compiler wants to link to the library compiled by the second compiler, it must first recompile the above through the first compiler. Library. However, in the absence of the source code, the above library cannot be recompiled. To this end, the present invention proposes a method of executing a user space program and a computer system using the same, which can link a library compiled by different compilers without recompiling. In order to clarify the content of the present invention, the following specific examples are given as examples in which the present invention can be implemented.

First embodiment

1 is a schematic diagram of a computer system in accordance with a first embodiment of the present invention. Referring to FIG. 1 , the computer system 100 has a user space 110 and a core 130 . Computer system 100 is, for example, an embedded system.

The user space 110 has a first program 111 and a second program 121. The first program 111 is coupled to the first standard library 113, and the first program 111 and the first standard library 113 are compiled by the first compiler. The second program 121 is coupled to the second standard library 123, and the second program 121 and the second standard library 123 are compiled by the second compiler.

In the user space 110, the third-party library 141 provided by the manufacturer may be included, and the hardware output interface on the computer system 100 may be controlled, which is dependent on the second standard library 123.

The core 150 provides the file system module 151, so that the first program 111 communicates with the second program 121 through the file system module 151 and the second program 121 provided by the core 150, and then connects to the third party by using the second program 121. Library 141. This is because the first standard library 113 is not compatible with the second standard library 123, so the first program 111 cannot directly link to the third party library 141 to use the functions it provides. In addition, in the user space 110, the file system library 131 corresponding to the file system module 151 provided by the core 150 is further present.

The file system module 151 is, for example, a Filesystem in Userspace (FUSE) module, which provides a framework for developers to develop a file system in a Linux system, enabling developers to quickly develop and use in the user space 110. Test the file system. The FUSE architecture mainly has two tools, one is the file system module 151 in the core 150, and the other is the structure in the user space 110 for providing the relevant functions of the file system module 151 to the developer. File System Library 131.

The second program 121 registers the virtual file system 153 with the file system module 151 through the file system library 131, so that the first program 111 can use the virtual file system 153 and use the third program library 141 through the second program 121.

Here, the file system module 151 of the core 150 can be used by the first standard library 113 and the second standard library 123 compiled by different compilers by means of a system call. The system call provides an interface between the program in user space 110 and core 150. Most system interactive operation requirements are performed at core 150, such as device operations or different program communications. The space of the operating system can be divided into user space 110 and core 150, which require different execution permissions. The system call runs on core 150.

The following is a detailed description of the steps of the method for executing the user space program in conjunction with the computer system 100 described above. 2 is a flow chart of a method of executing a user space program in accordance with a first embodiment of the present invention. Referring to FIG. 1 and FIG. 2 simultaneously, in step S205, the second program 121 registers the virtual file system 153 with the file system module 151 through the file system library 131.

Specifically, the second program 121 calls the registration function of the file system library 131, and transmits the file system path and the function index of the second standard library 123 through the registration function. Then, the registration function transmits an open request to the core 150 through the open function of the second standard library 123. When the core 150 receives the open request, the virtual device provided by the file system module 151 is opened according to the open request, and the virtual device is used to transfer the file descriptor to the second program 121. At this time, the second program 121 transmits a setup request to the core 150 through the control function of the second standard library 123 to establish the virtual file system 153 according to the virtual device path.

After the registration of the second program 121 is completed, in step S210, the first program 111 transmits an operation request to the second program 121 through the virtual file system 153 to notify the second program 121 that it wants to use the third party library 141. The file system path of the second program 121 is included in the operation request. For example, the first program 111 calls the function of the first standard library 111 to transmit an operation request to the file system module 151 through the virtual file system 153. Thereafter, the file system module 151 transfers the operation request to the second program 121 in accordance with the file system path.

After the second program 121 receives the operation request, as shown in step S215, the second program 121 is linked to the third-party library 141 according to the operation request, thereby executing the corresponding function in the third-party library 141. Specifically, after registering with the file system module 151, the second program 111 calls the wait function of the file system library 131 to poll the virtual file system 153 for receiving an operation request. If the second program 111 polls the virtual file system 153 to receive the operation request, the processing function of the call file system library 131 parses the operation request to link to the third party library 141 according to the operation request.

Thereafter, in step S220, the second program 121 transmits a response to the first program 111 through the virtual file system 153. For example, the second program 121 passes back the file descriptor (File Descriptor) obtained by executing the operation request to the first program 111 through the core 150.

Second embodiment

3A-3C are schematic diagrams showing a method of executing a user space program according to a second embodiment of the present invention. FIG. 3A is a schematic diagram of a process of registering a virtual file system, and FIG. 3B and FIG. 3C are schematic diagrams showing a process of opening a virtual file system.

The general Linux kernel common compilers are the GNU Compiler Collection (GNU Compiler Collection, called GCC compiler) and GNU's GLIBC loader. The Android system is a software platform and operating system based on the Linux kernel. It uses the self-developed BIONIC compiler and BIONIC loader.

In this embodiment, the core 304 of the Android system provides a FUSE module 305, and the FUSE module 305 has a corresponding FUSE library 302 in the user space. The user space includes a first program 306 and a second program 301. The first program 306 is a program compiled by the BIONIC compiler that can be linked to the BIONIC library 307 compiled by the BIONIC compiler. The second program 301 is a program compiled by the GCC compiler, which can be linked to the GLIBC library 303 compiled by the GCC compiler.

Here, the second program 301 can register a virtual file system with the FUSE module 305 of the core 304. Referring to FIG. 3A, as shown in step S311, the second program 301 will call the FUSE library 302 registration function "fuse_register" to register with the FUSE module 305. The second program 301, when calling the registration function "fuse_register", will pass in a file system path (for example, "/root/FS2" under the root directory) and its file operation function indicators (for example, vfs_open, vfs_read and Vfs_close, etc.). Next, in step S313, the registration function "fuse_register" will open the virtual device (for example, "/dev/fuse") provided by the FUSE module 305 through the open function "open" of the GLIBC library 303.

Thereafter, the open function "open" of the GLIBC library 303 issues a start request to the core 304 using the system call "syscall_open", as shown in step S315. Then, the core 304 belongs to the virtual device provided by the FUSE module 305 according to the file to be opened, so the open request "syscall_open" is handed over to the open function "fuse_open" of the FUSE module 305, and the result is returned. The file descriptor "fd" is given to the second program 301 of the user space, indicating that the file information is opened, as in step S319.

Then, in step S321, the second program 301 issues a setup request "CREAT" to the file descriptor "fd" of the virtual device of the opened FUSE module 305 through the control function "ioctl" of the GLIBC library 303. Next, the control function "ioctl" of the GLIBC library 303 will issue a setup request to the core 304 using the system call "syscall_ioctl", as shown in step S323. Thereafter, the core 304 processes the setup request to the virtual device of the FUSE module 305 according to the opened file description "fd", and passes the setup request to the control function "fuse_ioctl" of the FUSE module 305, as shown in step S325.

Then, in step S327, the control function "fuse_ioctl" of the FUSE module 305 will surely create a virtual file according to the number of the parameter "CREATE" and the file system path (such as "/root/GmailFS" under the root directory). The tree structure of the system. After that, the return is successful or not, as shown in step S329.

Then, the second program 301 will continuously call the wait function "fuse_wait_req" of the FUSE library 302 to wait for another program to operate the virtual file system. For example, by waiting for the function "fuse_wait_req" to poll the virtual file system for receiving an operation request for any program, as shown in steps S331 to S339. In step S331, the second program 201 calls the wait function "fuse_wait_req" of the FUSE library 302. Next, in step S333, the wait function "fuse_wait_req" issues a wait request "wait_req" according to the file descriptor "fd" through the control function "ioctl" of the GLIBC library 303. Thereafter, the control function "ioctl" of the GLIBC library 303 will use the system call "syscall_ioctl" to the core 304, as shown in step S335. The core 304 then hands the system call "syscall_ioctl" to the wait function "fuse_wait_req" of the FUSE module 305.

At this time, the virtual file system established by the second program 301 through the FUSE module 305 can be seen on the file system. Accordingly, other programs can operate the registered virtual file system through the FUSE module 305.

Referring to FIG. 3B, the first program 306 opens the virtual file system through the FUSE module 305. In step S341, the first program 306 first calls the open function "open" of the BIONIC library 307 to transmit an operation request (the operation request is, for example, to open the file), and passes the file system path to be opened as a parameter. Next, as shown in step S343, the open function "open" of the BIONIC library 307 transmits the file system path to the core 304 using the system call "syscall_open". Then, the core 304 receives the operation request, and determines that the file of the file system path is the file format registered with the FUSE module 305. Therefore, the action of opening the file is processed by the FUSE module 305, and then the FUSE module 305 is called. The function "fuse_req_open" is opened, as shown in step S345.

The file location where the FUSE module 305 receives the operation request is the virtual file system belonging to the second program 301, so the operation request is forwarded to the second program 301 by using the forwarding function "fuse_redirect_req", as shown in step S347. At this time, the FUSE module 305 will end the waiting of step S339 in FIG. 3A. That is, when the wait function "fuse_wait_req" polls the virtual file system to receive the operation request of the first program 301, the processing function "fuse_proce_req" of the FUSE library 302 is called to parse the operation request. And, the FUSE module 305 calls the wait response function "fuse_wait_resp" as shown in step S349. Thereafter, the FUSE module 305 will return a file descriptor "fd" to the first program 306, as shown in step S351.

Referring to FIG. 3C, in step S353, the FUSE library 302 calls the processing function "fuse_proce_req" according to the result of the wait response function "fuse_wait_req", and the operation request is to open the file, and the FUSE library 302 is based on the The function indicator of the file operation previously registered by the second program 301 calls the corresponding open function "vfs_open", and the result will return a file descriptor "fd", as shown in step S357, according to which the file can be opened. .

Thereafter, in step S359, the FUSE library 302 calls the response function "fuse_resp_req". And, in step S361, the control function "ioctl" of the GLIBC library 303 is called. Next, in step S363, the control function "ioctl" of the GLIBC library 303 transmits the file descriptor of the open function "vfs_open" to the core 304 using the system call "syscall_ioctl". Then, in step S365, the control function "fuse_ioctl" of the FUSE module 305 is called. At this time, the FUSE module 305 will end the waiting of step S349 in FIG. 3B. Finally, the core 304 returns the information of the open file.

That is, the second program 301 registers the file system provided by the FUSE module 305. Accordingly, the first program 306 can open, read, write, control (ioctl) and close (close) the virtual file system created by the second program 301 through the FUSE module 305. All of its processes will eventually call the previously registered function indicators of the second program 301 (for example, vfs_open, vfs_read, vfs_close, etc.).

Third embodiment

4 is a schematic diagram of a computer system in accordance with a third embodiment of the present invention. Referring to FIG. 4, the computer system 400 has a user space 410 and a core 430. The user space 410 has a first program 411 and a second program 421. The first program 411 is a program compiled by the BIONIC compiler, which can be linked to the BIONIC library 413 compiled by the BIONIC compiler. The second program 421 is a program compiled by the GCC compiler that can be linked to the GLIBC library 423 compiled by the GCC compiler.

In the user space 110, for example, the third-party library 141 corresponding to the GLIBC library 423 provided by the manufacturer, the FUSE library 431 corresponding to the FUSE module 451 provided by the core 450, and the like may be included. Extensible Markup Language (XML) library 433.

In the computer system 400, an XML format of a FUSE remote program call request (FUSE_RPCQ) is customized, which includes the called library name, function name, parameter type, and parameter data. Figure 5 is a diagram showing an XML format in accordance with a third embodiment of the present invention. Referring to Figure 5, the root tag of the XML is <FuseRpcq>, which indicates the beginning of the file. The attribute "name" of the label "Library" is used to define the name of the library to be called; the attribute "name" of the label "Function" is used to define the name of the function of the call; the attribute "type" of the label "Param" is used to define The parameter type of the call function, the attribute "name" is used to define the parameter name. Here, assume that the library name of the third-party library 441 is "libgbt_display.so". In this X ML file, the function "clear_screen" is used to clear the screen, the function "show_image" is used to display the image, and the function "show_image" contains the position, size and file path of the displayed image.

Returning to FIG. 4, the second program 421 registers the virtual file system 453 with the FUSE module 451. After that, the first program 411 starts the virtual file system established by the FUSE module 451, and the first program executes the system call through the control function "ioctl" of the BIONIC library 413, and the XML file "FuseRpcq" is used as the XML file. The parameters are passed to the FUSE module 451, and the first program 411 then waits for a response from the FUSE module 451.

The FUSE module 451, after receiving the request of the first program 411, forwards the request to the second program 421. At this time, the second program 421 will call the processing function of the FUSE library 431 and parse the XML file "FuseRpcq" according to the XML library 433, thereby dynamically linking to the library name in the XML file "FuseRpcq". The third party library 441 calls the function "clear_screen" of the third party library 441 and the call function "show_image". After that, the second program 421 will return a response to the first program 411. The first program 411 will end the system call performed by the control function "ioctl" upon receiving the response.

In the above manner, the first program 411 can smoothly call a library that cannot be linked with the program compiled by BIONIC, and reduce the code size to change the call flow into an XML file exchange. Also, multiple programs can use the virtual file system 453 at the same time.

In addition, the above embodiments may be implemented in the form of a computer program product (eg, software, firmware, etc.), and the user space program may be stored by using a computer-readable recording medium (eg, a CD, a hard disk, a memory, etc.). Eli is implemented by the computer system and is done electronically. Specifically, the computer can read the recording medium for storing the user space program to load the computer system to execute. The user space program includes a first program and a second program, and the computer system includes a user space and a core. The user space includes a first program, wherein the first program is linked to the first standard library, and the first program and the first standard library are compiled by the first compiler. The method for executing the user space program includes: providing a second program and a third-party library in the user space, wherein the second program is linked to the second standard library, and the second program and the second standard library are Compiled by the second compiler, and the third-party library is dependent on the second standard library. The first program will communicate with the second program through the file system module provided by the core to connect to the third-party library through the second program. The file system module has a corresponding file system library in the user space. . The steps of the first program to be linked to the third-party library through the second program are as shown in steps S205 to S220 of the first embodiment, and therefore are not described herein again.

In summary, in the above embodiment, the file system module provided by the core enables the first program and the second program compiled by different compilers in the user space to communicate, and then utilizes the communication mode to make the first The program calls the second program and connects to the third-party library through the second program. Accordingly, without recompiling the third-party library, the first program can call the third-party library through the help of the second program. Moreover, there is no need to modify the core to keep the system stable and also reduce development costs.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the invention, and any one of ordinary skill in the art can make some modifications and refinements without departing from the spirit and scope of the invention. The scope of the invention is defined by the scope of the appended claims.

100, 400. . . computer system

110, 410. . . User space

111, 306, 411. . . First program

113. . . First standard library

121, 301, 421. . . Second program

123. . . Second standard library

131. . . File system library

141, 441. . . Third-party library

150, 304, 450. . . core

151. . . File system module

153, 453. . . Virtual file system

302, 431. . . FUSE library

303, 423. . . GLIBC library

305, 451. . . FUSE module

307, 413. . . BIONIC library

433. . . XML library

S205~S220. . . Each step of the method for executing a user space program in the first embodiment of the present invention

S311~S365. . . Method for performing a user space program according to a second embodiment of the present invention

1 is a schematic diagram of a computer system in accordance with a first embodiment of the present invention.

2 is a flow chart of a method of executing a user space program in accordance with a first embodiment of the present invention.

3A-3C are schematic diagrams showing a method of executing a user space program according to a second embodiment of the present invention.

4 is a schematic diagram of a computer system in accordance with a third embodiment of the present invention.

Figure 5 is a diagram showing an XML format in accordance with a third embodiment of the present invention.

S205~S220. . . Each step of the method for executing a user space program in the first embodiment of the present invention

Claims (10)

A method for executing a user space program is applicable to a computer system including a user space and a core, the user space including a first program, wherein the first program is coupled to a first standard function a library, and the first program and the first standard library are compiled by a first compiler, the method comprising: providing a second program and a third-party library in the user space, wherein the first The second program is linked to a second standard library, and the second program and the second standard library are compiled by a second compiler, and the third-party library is dependent on the second standard library. The first program communicates with the second program by a file system module provided by the core to connect to the third party library through the second program, wherein the file system module is in the user space There is a corresponding file system library, and the step of linking the first program to the third party library through the second program comprises: registering the second program with the file system module through the file system library a virtual file The first program transmits an operation request to the second program through the virtual file system; the second program is linked to the third-party library according to the operation request, thereby executing a corresponding letter in the third-party library And the second program transmits a response to the first program through the virtual file system. The method for executing a user space program as described in claim 1, wherein the step of registering the virtual file system with the file system module by the second program through the file system library comprises: the second program call a registration function of the file system library to transmit a file system path and a function indicator of the second standard library; the registration function is opened by an open function of the second standard library The core transmits an open request; the core opens a virtual device according to the open request, so that the virtual device transmits an operation descriptor to the second program; and the second program transmits a control function of the second standard library An establishment request is transmitted to the core to establish the virtual file system according to the file system path. The method for executing a user space program according to the first aspect of the invention, wherein after the step of registering the virtual file system with the file system module by using the file system library, the method further comprises: The second program calls a wait function of the file system library to poll the virtual file system for receiving the operation request. The method for executing a user space program according to claim 3, wherein the second program is linked to the third party library according to the operation request, thereby executing a corresponding function in the third party library. Before the step, the method further includes: if the waiting program polls the virtual file system to receive the operation request, calling a processing function of the file system library to parse the operation request. The method for executing a user space program according to claim 1, wherein the step of transmitting, by the first program, the operation request to the second program through the virtual file system comprises: the first program calling the first standard a function of the library to transmit the operation request to the file system module through the virtual file system, wherein the operation request includes a file system path; and the file system module transmits the operation request to the file system path according to the file system The second program. The method for executing a user space program as described in claim 1, wherein the file system module is a user space file system module. The method for executing a user space program according to claim 1, wherein the operation request is in an Extensible Markup Language (XML) format. A computer system comprising: a core, comprising: a file system module; and a user space, comprising: a file system library corresponding to the file system module; a first program, linked to a first a standard library, wherein the first program and the first standard library are compiled by a first compiler; a second program is coupled to a second standard library, wherein the second program and the second The second standard library is compiled by a second compiler; and a third-party library is dependent on the second standard library; wherein the second program is configured to the file system through the file system library Registering a virtual file system, the first program is capable of transmitting an operation request to the second program through the virtual file system; and the second program is linked to the third party library according to the operation request, thereby executing the first The corresponding function in the tripart library; afterwards, the second program transmits a response to the first program through the virtual file system. The computer system of claim 8, wherein the operation request is in the form of an Extensible Markup Language (XML). A computer-readable recording medium for storing a user space program for a computer system, the computer system comprising a user space and a core, the user space comprising a first program, wherein the first program Linking to a first standard library, and the first program and the first standard library are compiled by a first compiler, the method comprising: providing a second program and a first in the user space a third-party library, wherein the second program is linked to a second standard library, and the second program and the second standard library are compiled by a second compiler, and the third-party library is dependent In the second standard library, the first program communicates with the second program by a file system module provided by the core to connect to the third party library through the second program, wherein the file system The module has a corresponding file system library in the user space, and the step of connecting the first program to the third party library through the second program includes: the second program is transmitted through the file system function Library to the file The system module registers a virtual file system; the first program transmits an operation request to the second program through the virtual file system; the second program is linked to the third party library according to the operation request, thereby executing the third party a corresponding function in the library; and the second program transmits a response to the first program through the virtual file system.