WO2023179509A1 - Data access apparatus and method, and readable medium and electronic device - Google Patents

Abstract

The present disclosure relates to a data access apparatus and method, and a readable medium and an electronic device. The data access apparatus comprises a Fuse module, a plurality of first socket interfaces and a memory. The Fuse module communicates with the memory by means of the plurality of first socket interfaces. The Fuse module and the first socket interfaces are located in a kernel space. The Fuse module is used for receiving a data access request, and determining, from among the plurality of first socket interfaces, a target socket interface corresponding to the data access request. The Fuse module is further used for acquiring target data from the memory using the target socket interface and sending the target data to a target application program. In the present disclosure, target data can be acquired from a memory by means of a Fuse module according to a data access request and by using a target socket interface, there is no need to perform transfer in a user space, and the data access request can be directly sent in a kernel space to the memory, thereby improving the access performance for the target data.

Description

Data access apparatus, method, readable medium and electronic device

This disclosure claims priority to the Chinese patent application filed with the China Patent Office on March 25, 2022, with application number 202210307683. incorporated by reference into this disclosure.

Technical field

The present disclosure relates to the field of computer technology, and specifically, to a data access device, a method, a readable medium, an electronic device, a computer program and a computer program product.

Background technique

Under the architecture of computing and storage separation, when a computing node needs to access the services provided by distributed file storage, it usually needs to mount a Fuse (English: Filesystem in Userspace, Chinese: User Space File System) module to achieve access. Access requests to this distributed file storage will be intercepted by the kernel's Fuse module and forwarded to the user-mode Daemon (Chinese: process). Then, the user-mode Daemon sends the access request to the backend of the distributed file storage through the network to complete the data access. However, using this method, the file access request needs to be transferred from the user-space Daemon and then sent through the network. This process will involve multiple copies, system calls, context switches and other operations, which will affect the access to the data. Access performance.

Contents of the invention

This section is provided to introduce in simplified form concepts that are further described in the Detailed Description. This section is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to be used to limit the scope of the claimed technical solution.

In a first aspect, the present disclosure provides a data access device. The data access device includes a user space file system Fuse module, a plurality of first socket interfaces, and a memory. The Fuse module passes a plurality of the first sockets. The word interface communicates with the memory, and the Fuse module and the first socket interface are located in the kernel space;

The Fuse module is configured to receive a data access request for target data from a target application, and determine a target socket interface corresponding to the data access request from a plurality of the first socket interfaces;

The Fuse module is also used to obtain the target data from the memory using the target socket interface, and send the target data to the target application program to complete data access.

In a second aspect, the present disclosure provides a data access method, applied to the device described in the first aspect, the method includes:

Receive a data access request for target data from a target application program through the Fuse module, and determine the target socket interface corresponding to the data access request from a plurality of the first socket interfaces;

The Fuse module utilizes the target socket interface to obtain the target data from the memory, and sends the target data to the target application program to complete data access.

In a third aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, and when the program is executed by a processing device, the steps of the method described in the second aspect of the present disclosure are implemented.

In a fourth aspect, the present disclosure provides an electronic device, including:

a storage device having at least one computer program stored thereon;

At least one processing device, configured to execute the at least one computer program in the storage device to implement the steps of the method described in the second aspect of the present disclosure.

In a fifth aspect, the present disclosure provides a computer program, the computer program comprising a program code executable by a processing device, and when the processing device executes the computer program, the steps of the method of the second aspect are implemented.

In a sixth aspect, the present disclosure provides a computer program product. The computer program product includes a computer program carried on a non-transitory computer-readable medium. The computer program includes program code executable by a processing device. When the processing device executes The computer program implements the steps of the method of the second aspect.

Other features and advantages of the present disclosure will be described in detail in the detailed description that follows.

Description of the drawings

The above and other features, advantages, and aspects of various embodiments of the present disclosure will become more apparent with reference to the following detailed description taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and elements are not necessarily drawn to scale. In the attached picture:

Figure 1 is a block diagram of a data access device according to an exemplary embodiment;

Figure 2 is a block diagram of another data access device according to an exemplary embodiment;

Figure 3 is a flow chart of a data access method according to an exemplary embodiment;

Figure 4 is a flow chart of step 201 according to the embodiment shown in Figure 3;

Figure 5 is a flow chart of yet another step 201 according to the embodiment shown in Figure 3;

FIG. 6 is a block diagram of an electronic device according to an exemplary embodiment.

Detailed ways

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the disclosure are shown in the drawings, it should be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, which rather are provided for A more thorough and complete understanding of this disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that various steps described in the method implementations of the present disclosure may be executed in different orders and/or in parallel. Furthermore, method embodiments may include additional steps and/or omit performance of illustrated steps. The scope of the present disclosure is not limited in this regard.

As used herein, the term "include" and its variations are open-ended, ie, "including but not limited to." The term "based on" means "based at least in part on." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; and the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below.

It should be noted that concepts such as “first” and “second” mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units. Or interdependence.

It should be noted that the modifications of "one" and "plurality" mentioned in this disclosure are illustrative and not restrictive. Those skilled in the art will understand that unless the context clearly indicates otherwise, it should be understood as "one or Multiple”.

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are for illustrative purposes only and are not used to limit the scope of these messages or information.

All actions to obtain signals, information or data in this disclosure are carried out in compliance with the corresponding data protection regulations and policies of the country where they are located, and with the authorization given by the owner of the corresponding device.

FIG. 1 is a block diagram of a data access device according to an exemplary embodiment. As shown in Figure 1, the data access device 100 includes a Fuse module 101, a plurality of first socket interfaces 102, and a memory 103. The Fuse module 101 communicates with the memory 103 through a plurality of first socket interfaces 102. The Fuse module 101 and the first socket interface 102 are located in kernel space.

The Fuse module 101 is configured to receive a data access request for target data from a target application program, and determine the target socket interface corresponding to the data access request from a plurality of first socket interfaces 102 .

For example, for distributed file storage, a file presented on a computing node is usually in the form of shards, so that different file segments are stored on different storage backend nodes. In other words, reading and writing a certain file segment can actually be sent and received through a specific Socket (Chinese: socket) interface. Therefore, you can use Fuse The module senses the mapping relationship between file sections and Sockets, thereby bypassing the user-mode Daemon and directly sending file read and write requests to the storage back-end node through the Socket interface in the kernel to improve data access performance.

Specifically, under the computing and storage separation architecture, data is stored in the remote memory 103. When the target application needs to access the target data in the target file locally, it can first access the target data through the mount point of the target application (English). :Mount Point), the data access request for the target data is sent to the VFS (English: Virtual File System, Chinese: Virtual File System) in the kernel, and the VFS sends the data access request to the Fuse module 101. Then, the Fuse module 101 can determine the target socket interface from the plurality of first socket interfaces 102 in the kernel according to the data access request. For example, when the data access request is the file section where the target data is located in the target file, the corresponding relationship between the file section and the first socket interface 102 can be established in advance. After receiving the data access request, The Fuse module 101 can use the corresponding relationship to determine the target socket interface from the plurality of first socket interfaces 102 according to the location of the target data in the target file.

The Fuse module 101 is also used to obtain target data from the memory 103 using the target socket interface, and send the target data to the target application program to complete data access.

For example, the Fuse module 101 can directly send the data access request to the remote storage 103 through the network using the target socket interface. Among them, the memory 103 may be a remote memory (English: Remote Storage). After receiving the data access request, the memory 103 can obtain the stored target data according to the data access request, and return the target data to the Fuse module 101 through the target socket interface. Afterwards, the Fuse module 101 can send the received target data to the VFS, and the VFS returns the target data to the target application to complete the data access.

It should be noted that the Fuse module 101 directly sends the data access request to the memory 103 through the target socket interface. In fact, a fast link consisting of the VFS, the Fuse module 101, the first socket interface 102 and the memory 103 is established. Path, this fast path does not need to be transferred by the user-mode Daemon, and can avoid multiple copies, system calls, context switches and other operations involved in the user-mode Daemon transfer process, thereby improving the access performance of data.

To sum up, the data access device in the present disclosure includes a Fuse module, a plurality of first socket interfaces and a memory. The Fuse module communicates with the memory through a plurality of first socket interfaces. The Fuse module and the first socket The word interface is located in the kernel space. The Fuse module is used to first receive the data access request for the target data from the target application, and then determine the target socket interface corresponding to the data access request from multiple first socket interfaces, and then use The target socket interface obtains the target data from the memory and sends the target data to the target application to complete the data access. This disclosure can use the Fuse module to obtain the target from the memory according to the data access request using the target socket interface. The data does not need to be transferred in user space, and the data access request can be sent directly to the memory in the kernel space, which improves the access performance of the target data.

Optionally, the data access request may include the file section where the target data is located in the target file to which the target application program wants to perform data access. Among them, the Fuse module 101 is used to determine whether there is a target socket interface corresponding to the file section from a plurality of first socket interfaces 102 by using a preset correspondence relationship according to the file section, and determine whether the target socket interface exists. In the case of a socket interface, the data access request is sent to the memory 103 using the target socket interface. The default correspondence relationship is the correspondence relationship between the file section and the first socket interface.

For example, the data access request is actually used to tell the memory 103 the location of the target data to be obtained by the target application program in the target file. In order to improve the performance of data access, multiple fast paths can be established in the kernel in advance, and these established fast paths can be recorded by building preset correspondences. The preset corresponding relationship may be a mapping table. For example, the mapping table may include a corresponding relationship between the file section and the first socket interface. In the case where the data access request includes the file section where the target data is located in the target file, when the data access request passes through the Fuse module 101 of the kernel, the Fuse module 101 can use the preset correspondence relationship to extract data from multiple files based on the file section. In a first socket interface 102, it is determined whether there is a target socket interface corresponding to the file section. If there is a target socket interface, the Fuse module 101 can use the target socket interface to send the data access request to the memory 103 according to the communication protocol corresponding to the target socket interface. Among them, the communication protocol may be TCP/IP (English: Transmission Control Protocol/Internet Protocol, Chinese: Transmission Control Protocol/Internet Protocol) protocol.

It should be noted that the process by which the Fuse module 101 determines whether a target socket interface exists is actually the process by which the Fuse module 101 determines whether a fast path exists by querying a preset correspondence (such as a mapping table). If a target socket exists word interface, it means that there is a fast path, then the data access request for the file section capable of executing the fast path can be sent to the memory 103 through the target socket interface alone. That is to say, this disclosure actually generates a fast path for data access by the Fuse module 101 by establishing a preset correspondence in the kernel, and directly sends the data access request for the target file to the memory 103 through the socket interface in the kernel. , instead of forwarding it to the user-mode Daemon, which improves the access performance to the target data.

Figure 2 is a block diagram of another data access device according to an exemplary embodiment. As shown in Figure 2, the data access device 100 also includes a Fuse Daemon module 104 and a second socket interface 105. The Fuse Daemon module 104 communicates with the memory 103 through the second socket interface 105. The Fuse Daemon module 104 and the second socket interface 105 communicate with each other. Socket interface 105 resides in user space.

The Fuse module 101 is also used to send the data access request to the Fuse Daemon module 104 when it is determined that the target socket interface does not exist.

The Fuse Daemon module 104 is used to obtain target data from the memory 103 using the second socket interface 105 and send the target data to the target application.

In one scenario, if the target socket interface does not exist, it means that the file section included in the data access request is a file section that cannot execute the fast path. Then the data access request can be forwarded to the user mode according to the original processing method. Daemon for processing. That is to say, the Fuse module 101 can send the data access request to the Fuse Daemon module 104 for transfer when it is determined that the target socket interface does not exist. The Fuse Daemon module 104 can then use the second socket interface 105 corresponding to the data access request to send the data access request to the memory 103 through the TCP/IP protocol corresponding to the second socket interface 105. After receiving the data access request, the memory 103 can obtain the stored target data according to the data access request, and return the target data to the target through the second socket interface 105, the Fuse Daemon module 104, the Fuse module 101 and the VFS. application to complete data access. In addition, if the communication process of the multiple first socket interfaces 102 of the kernel is abnormal (for example, the connection is closed or the request times out), the Fuse module 101 also needs to forward the data access request of the file section that can execute the fast path. Go to Fuse Daemon module 104 for processing.

It should be noted that the transfer of data access requests through the Fuse Daemon module 104 actually establishes a slow path composed of VFS, Fuse module 101, Fuse Daemon module 104, second socket interface 105 and memory 103 . Moreover, the present disclosure distinguishes between the socket interface of the fast path and the socket interface of the slow path, which facilitates compatibility with the original communication method and does not require changing the data format sent and received by the slow path to the Fuse request format.

Optionally, the Fuse Daemon module 104 is also used to obtain the communication information corresponding to the data access request from the memory 103 after sending the target data to the target application, and construct a new first socket interface 102 based on the communication information, And register the new first socket interface 102 into the kernel space. Among them, the communication information includes communication address and communication port.

For example, establishing a corresponding relationship in the kernel is the core of completing data access, that is, a new first socket interface 102 needs to be established in the kernel. Specifically, after the Fuse Daemon module 104 completes a data access, the communication information corresponding to the data access request can be obtained from the memory 103, and then a new first socket interface 102 can be established in the kernel based on the communication information. That is, a new Socket connection is established.

The Fuse Daemon module 104 can then notify the memory 103 that these new connections are for the fast path. After the memory 103 agrees on the new connection for the fast path, the Fuse Daemon module 104 can register the new first socket interface 102 into kernel space. The communication information may include a communication address and a communication port. The communication address may be an IP address, for example, and the communication port may be a TCP port, for example.

Further, multiple types of user-mode interfaces for establishing fast paths can be set in the Fuse module 101. For example, four user-mode interfaces can be provided in the Fuse module 101 to establish or adjust the fast path. Specifically, the following four user-mode interfaces can be included:

1) FUSE_ADD_FAST_PATH, used to register a new fast path with the kernel. The input is: the file handle (Chinese: file handle) corresponding to the opened target file, the starting position of the target file that needs to be mapped, the file length of the mapped target file, the Socket fd (English: file descriptor) array that needs to be mapped, and The array length of the Socket fd that needs to be mapped. The output is: if successful, an id is returned to identify the fast path, and if it fails, an error code is returned. It should be noted that the fast path is established based on the file handle of the target file as the object, rather than the inode of the target file. This mainly facilitates process-level control (for example: only allowing certain user processes to use the fast path). At the same time, it is also allowed to register multiple Socket fds for the same file section. In this case, the kernel needs to send the file request to all corresponding Sockets.

2) FUSE_REMOVE_FAST_PATH, used to delete the fast path registered by the kernel. The input is: the id corresponding to the fast path. The output is: 0 is returned if successful, and an error code is returned if failed. It should be noted that after the corresponding target file is closed, the corresponding fast path will be automatically deleted by the kernel.

3) FUSE_UPDATE_FAST_PATH is used to update the default correspondence established by the kernel. Its input is: the id corresponding to the fast path, the Socket fd array that needs to be mapped, and the array length of the Socket fd that needs to be mapped. The output is: 0 is returned if successful, and an error code is returned if failed.

4) FUSE_QUERY_FAST_PATH, used to query the fast path registered by the kernel. The input is: the file handle corresponding to the target file, the starting position of the target file that needs to be mapped, and the file length of the mapped target file. The output is: if the corresponding fast path exists, the id corresponding to the fast path, the starting position of the actual mapped target file, the length of the actual mapped target file, and the Socket fd list are returned. If it does not exist, -1 is returned.

To sum up, the data access device in the present disclosure includes a Fuse module, a plurality of first socket interfaces and a memory. The Fuse module communicates with the memory through a plurality of first socket interfaces. The Fuse module and the first socket The word interface is located in the kernel space. The Fuse module is used to first receive the data access request for the target data from the target application, and then determine the target socket interface corresponding to the data access request from multiple first socket interfaces, and then use The target socket interface obtains the target data from the memory and sends the target data to the target application to complete the data access. This disclosure can use the Fuse module to obtain target data from the memory according to the data access request, and does not need to be transferred in the user space. It can directly send the data access request to the memory in the kernel space, improving the accuracy of the target. Data access performance.

Figure 3 is a flow chart of a data access method according to an exemplary embodiment. As shown in Figure 3, applied to any of the above data access devices, the method may include the following steps:

Step 201: Receive a data access request for target data from the target application program through the Fuse module, and determine the target socket interface corresponding to the data access request from a plurality of first socket interfaces.

Step 202: Use the Fuse module to obtain the target data from the memory using the target socket interface, and send the target data to the target application to complete the data access.

Optionally, the data access request includes the file section where the target data is located in the target file to be accessed by the target application. Step 201 can be implemented in the following manner:

The Fuse module uses the preset correspondence relationship according to the file section to determine whether there is a target socket interface corresponding to the file section from multiple first socket interfaces, and determines whether the target socket interface exists In this case, the target socket interface is used to send the data access request to the memory. The default correspondence relationship is the correspondence relationship between the file section and the first socket interface.

Optionally, the step "when it is determined that the target socket interface exists, send the data access request to the memory using the target socket interface" can be implemented in the following manner:

Through the Fuse module, the data access request is sent to the memory using the target socket interface according to the communication protocol corresponding to the target socket interface.

FIG. 4 is a flow chart of another step 201 according to the embodiment shown in FIG. 3 . As shown in Figure 4, step 201 may include the following steps:

Step 2011: When it is determined that the target socket interface does not exist through the Fuse module, the data access request is sent to the Fuse Daemon module.

Step 2012, use the second socket interface to obtain the target data from the memory through the Fuse Daemon module, and send the target data to the target application.

FIG. 5 is a flow chart of yet another step 201 according to the embodiment shown in FIG. 3 . As shown in Figure 5, step 201 may also include the following steps:

Step 2013: After sending the target data to the target application through the Fuse Daemon module, obtain the communication information corresponding to the data access request from the memory, build a new first socket interface based on the communication information, and add the new first socket interface to the target application. The socket interface is registered in kernel space. Among them, the communication information includes communication address and communication port.

To sum up, the data access device in the present disclosure includes a Fuse module, a plurality of first socket interfaces and a memory. The Fuse module communicates with the memory through a plurality of first socket interfaces. The Fuse module and the first socket The word interface is located in the kernel space. The Fuse module is used to first receive data access requests for target data from the target application, and then from multiple In the first socket interface, determine the target socket interface corresponding to the data access request, then use the target socket interface to obtain the target data from the memory, and send the target data to the target application to complete the data processing. access. This disclosure can use the Fuse module to obtain target data from the memory according to the data access request, and does not need to be transferred in the user space. It can directly send the data access request to the memory in the kernel space, improving the accuracy of the target. Data access performance.

Referring now to FIG. 6 , a schematic structural diagram of an electronic device (such as the terminal device or server in FIG. 1 ) 600 suitable for implementing embodiments of the present disclosure is shown. Terminal devices in embodiments of the present disclosure may include, but are not limited to, mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (PDA, Personal Digital Assistant), tablet computers (PAD, tablet computers), portable multimedia players ( Mobile terminals such as PMP (Portable Multimedia Player), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), and fixed terminals such as digital televisions (TV, television), desktop computers, etc. The electronic device shown in FIG. 6 is only an example and should not impose any limitations on the functions and scope of use of the embodiments of the present disclosure.

As shown in Figure 6, the electronic device 600 may include a processing device (such as a central processing unit, a graphics processor, etc.) 601, which may process data according to a program stored in a read-only memory (ROM, Read Only Memory) 602 or from a storage device 608 The program loaded into the random access memory (RAM, Random Access Memory) 603 performs various appropriate actions and processes. In the RAM 603, various programs and data required for the operation of the electronic device 600 are also stored. The processing device 601, ROM 602 and RAM 603 are connected to each other via a bus 604. An input/output (I/O, Input/Output) interface 605 is also connected to bus 604.

Generally, the following devices can be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a Liquid Crystal Display (LCD) , an output device 607 such as a speaker, a vibrator, etc.; a storage device 608 including a magnetic tape, a hard disk, etc.; and a communication device 609. Communication device 609 may allow electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although FIG. 6 illustrates electronic device 600 with various means, it should be understood that implementation or availability of all illustrated means is not required. More or fewer means may alternatively be implemented or provided.

In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product including a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such embodiments, the computer program may be downloaded and installed from the network via communication device 609, or from storage device 608, or from ROM 602. When the computer program is executed by the processing device 601, the above functions defined in the method of the embodiment of the present disclosure are performed.

It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium may be, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any combination thereof. More specific examples of computer readable storage media may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard drive, random access memory (RAM), read only memory (ROM), removable Programmable read-only memory (EPROM (Erasable Programmable Read-only Memory) or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM, Compact Disc Read-only Memory), optical storage device, magnetic storage device, or the above Any suitable combination. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device . Program code embodied on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wire, optical cable, radio frequency (RF, Radio Frequency), etc., or any suitable combination of the above.

In some embodiments, the client and server can communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and can communicate with digital data in any form or medium. Communications (e.g., communications network) interconnections. Examples of communication networks include local area networks (LANs), wide area networks (WANs), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any current network for knowledge or future research and development.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device; it may also exist independently without being assembled into the electronic device.

The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: receives a data access request for target data from the target application program through the Fuse module, and Determine a target socket interface corresponding to the data access request from a plurality of first socket interfaces; use the target socket interface to obtain the target from the memory through the Fuse module data, and sends the target data to the target application to complete the data access.

Computer program code for performing operations of the present disclosure may be written in one or more programming languages, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++ also includes conventional procedural programming languages - such as "C" or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In situations involving remote computers, the remote computer can be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as an Internet service provider). connected via the Internet).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, segment, or portion of code that contains one or more logic functions that implement the specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown one after another may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagram and/or flowchart illustration, and combinations of blocks in the block diagram and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or operations. , or can be implemented using a combination of specialized hardware and computer instructions.

The modules involved in the embodiments of the present disclosure can be implemented in software or hardware. Among them, the name of the module does not constitute a limitation on the module itself under certain circumstances. For example, the Fuse module can also be described as "a module that receives data access requests for target data."

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: Field Programmable Gate Array (FPGA, Field Programmable Gate Array), Application Specific Integrated Circuit (ASIC, Application Specific Integrated Circuit), Application Specific Standard Product (ASSP, Application Specific Standard Product), System on Chip (SOC, System on Chop), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), etc.

In the context of this disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include electrical connections based on one or more wires, portable computer disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable Read memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

According to one or more embodiments of the present disclosure, Example 1 provides a data access device. The data access device includes a user space file system Fuse module, a plurality of first socket interfaces, and a memory. The Fuse module passes A plurality of first socket interfaces communicate with the memory, and the Fuse module and the first socket interface are located in the kernel space; the Fuse module is used to receive data access to target data from a target application. request, and determine the target socket interface corresponding to the data access request from a plurality of the first socket interfaces; the Fuse module is also used to use the target socket interface to obtain the data from the memory Obtain the target data and send the target data to the target application to complete the data access.

According to one or more embodiments of the present disclosure, Example 2 provides the apparatus of Example 1, the data access request includes a file section where the target data is located in a target file to be accessed by the target application. ; The Fuse module is used to determine whether there is a target socket interface corresponding to the file section from a plurality of the first socket interfaces by using a preset correspondence relationship according to the file section, And when it is determined that the target socket interface exists, use the target socket interface to send the data access request to the memory; the preset corresponding relationship is the file section and the Correspondence between first socket interfaces.

According to one or more embodiments of the present disclosure, Example 3 provides the device of Example 2. The Fuse module is configured to use the target socket interface to fuse the target socket interface according to the communication protocol corresponding to the target socket interface. The data access request is sent to the memory.

According to one or more embodiments of the present disclosure, Example 4 provides the device of Example 2. The data access device further includes a Fuse Daemon module and a second socket interface. The Fuse Daemon module passes through the second socket. The word interface communicates with the memory, and the Fuse Daemon module and the second socket interface are located in user space; the Fuse module is also used to, when it is determined that the target socket interface does not exist, The data access request is sent to the Fuse Daemon module; the Fuse Daemon module is used to obtain the target data from the memory using the second socket interface, and send the target data to the target application.

According to one or more embodiments of the present disclosure, Example 5 provides the apparatus described in Example 4, and the Fuse Daemon module is further configured to retrieve data from the memory after sending the target data to the target application. Obtain the communication information corresponding to the data access request, construct a new first socket interface based on the communication information, and register the new first socket interface in the kernel space; the communication The information includes communication addresses and communication ports.

According to one or more embodiments of the present disclosure, Example 6 provides a data access method, applied to the device described in any one of Examples 1 to 5, the method includes: receiving a target application through the Fuse module program target a data access request for target data, and determine a target socket interface corresponding to the data access request from a plurality of first socket interfaces; and utilize the target socket interface through the Fuse module Obtain the target data from the memory and send the target data to the target application program to complete the data access.

According to one or more embodiments of the present disclosure, Example 7 provides the method of Example 6, the data access request includes the file section where the target data is located in the target file to be accessed by the target application. Determining the target socket interface corresponding to the data access request from the plurality of first socket interfaces includes: using the Fuse module according to the file section, using a preset corresponding relationship , from a plurality of the first socket interfaces, determine whether there is a target socket interface corresponding to the file section, and if it is determined that the target socket interface exists, use the target socket interface The socket interface sends the data access request to the memory; the preset correspondence is the correspondence between the file section and the first socket interface.

According to one or more embodiments of the present disclosure, Example 8 provides the method of Example 7, wherein when it is determined that the target socket interface exists, the data access request is processed using the target socket interface. Sending to the memory includes: sending the data access request to the memory by using the target socket interface according to the communication protocol corresponding to the target socket interface through the Fuse module.

According to one or more embodiments of the present disclosure, Example 9 provides the method of Example 7, the data access device further includes a Fuse Daemon module and a second socket interface, and the method further includes: using the Fuse module to When it is determined that the target socket interface does not exist, the data access request is sent to the Fuse Daemon module; the Fuse Daemon module uses the second socket interface to obtain the data from the memory. Describe the target data and send the target data to the target application.

According to one or more embodiments of the present disclosure, Example 10 provides the method of Example 9, further comprising: using the Fuse Daemon module to obtain the target data from the memory after sending the target data to the target application. The communication information corresponding to the data access request, constructing a new first socket interface based on the communication information, and registering the new first socket interface into the kernel space; the communication information Including communication address and communication port.

According to one or more embodiments of the present disclosure, Example 11 provides a computer-readable medium having a computer program stored thereon, which implements the steps of the methods described in Examples 6 to 10 when executed by a processing device.

According to one or more embodiments of the present disclosure, Example 12 provides an electronic device, including: a storage device having at least one computer program stored thereon; and at least one processing device configured to execute the program in the storage device. A computer program to implement the steps of the methods described in Examples 6 to 10.

According to one or more embodiments of the present disclosure, Example 13 provides a computer program. The computer program includes program code executable by a processing device. When the processing device executes the computer program, Examples 6 to 10 are implemented. The steps of the method.

According to one or more embodiments of the present disclosure, Example 14 provides a computer program product, the computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program comprising a program executable by a processing device Code that implements the steps of the methods described in Examples 6 to 10 when the processing device executes the computer program.

The above description is only a description of the preferred embodiments of the present disclosure and the technical principles applied. Those skilled in the art should understand that the disclosure scope involved in the present disclosure is not limited to technical solutions composed of specific combinations of the above technical features, but should also cover solutions composed of the above technical features or without departing from the above disclosed concept. Other technical solutions formed by any combination of equivalent features. For example, a technical solution is formed by replacing the above features with technical features with similar functions disclosed in this disclosure (but not limited to).

Furthermore, although operations are depicted in a specific order, this should not be understood as requiring that these operations be performed in the specific order shown or performed in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims. Regarding the devices in the above embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Claims (12)

A data access device, including: a user space file system Fuse module, a plurality of first socket interfaces, and a memory; wherein the Fuse module communicates with the memory through a plurality of the first socket interfaces, The Fuse module and the first socket interface are located in the kernel space; The Fuse module is configured to receive a data access request for target data from a target application, and determine a target socket interface corresponding to the data access request from a plurality of the first socket interfaces; The Fuse module is also used to obtain the target data from the memory using the target socket interface, and send the target data to the target application program to complete data access. The apparatus according to claim 1, wherein the data access request includes a file section where the target data is located in a target file to which the target application program wants to perform data access; The Fuse module is configured to determine whether there is the target socket interface corresponding to the file section from a plurality of the first socket interfaces by using a preset correspondence relationship according to the file section. , and when it is determined that the target socket interface exists, use the target socket interface to send the data access request to the memory; the preset corresponding relationship is between the file section and the The corresponding relationship between the first socket interfaces is described. The device according to claim 2, wherein the Fuse module is configured to use the target socket interface to send the data access request to the memory according to the communication protocol corresponding to the target socket interface. . The device according to claim 2, wherein the data access device further includes a Fuse Daemon module and a second socket interface, the Fuse Daemon module communicates with the memory through the second socket interface, The Fuse Daemon module and the second socket interface are located in user space; The Fuse module is also configured to send the data access request to the Fuse Daemon module when it is determined that the target socket interface does not exist; The Fuse Daemon module is used to obtain the target data from the memory using the second socket interface, and send the target data to the target application. The device according to claim 4, wherein the Fuse Daemon module is further configured to obtain the communication information corresponding to the data access request from the memory after sending the target data to the target application, And construct a new first socket interface according to the communication information, and register the new first socket interface in the kernel space; the communication information includes a communication address and a communication port. A data access method, applied to the device according to any one of claims 1-5, the method comprising: Receive a data access request for target data from a target application program through the Fuse module, and determine the target socket interface corresponding to the data access request from a plurality of the first socket interfaces; and The target data is obtained from the memory by using the target socket interface through the Fuse module, And send the target data to the target application to complete the data access. The method of claim 6, wherein the data access request includes a file section in which the target data is located in a target file to be accessed by the target application, and the plurality of first Among the socket interfaces, determine the target socket interface corresponding to the data access request, including: The Fuse module uses the preset correspondence relationship according to the file section to determine whether there is the target socket interface corresponding to the file section from a plurality of the first socket interfaces, And when it is determined that the target socket interface exists, use the target socket interface to send the data access request to the memory; the preset corresponding relationship is the file section and the Correspondence between first socket interfaces. The method according to claim 7, wherein, when it is determined that the target socket interface exists, sending the data access request to the memory using the target socket interface includes: The Fuse module uses the target socket interface to send the data access request to the memory according to the communication protocol corresponding to the target socket interface. A computer-readable medium having a computer program stored on the computer-readable medium, wherein the steps of the method of any one of claims 6-8 are implemented when the computer program is executed by a processing device. An electronic device including: a storage device having at least one computer program stored thereon; At least one processing device, configured to execute the at least one computer program in the storage device to implement the steps of the method according to any one of claims 6-8. A computer program, the computer program comprising a program code executable by a processing device, when the processing device executes the computer program, the steps of the method of any one of claims 6-8 are implemented. A computer program product, the computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program comprising program code executable by a processing device, when the processing device executes the computer program Implement the steps of the method according to any one of claims 6-8.