CN115834713A - Interaction method and system for network file system and distributed file system - Google Patents

Interaction method and system for network file system and distributed file system Download PDF

Info

Publication number
CN115834713A
CN115834713A CN202310070104.9A CN202310070104A CN115834713A CN 115834713 A CN115834713 A CN 115834713A CN 202310070104 A CN202310070104 A CN 202310070104A CN 115834713 A CN115834713 A CN 115834713A
Authority
CN
China
Prior art keywords
task
file system
distributed file
network file
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310070104.9A
Other languages
Chinese (zh)
Inventor
刘爱贵
郭忠秋
阮薛平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dadao Yunxing Technology Co ltd
Original Assignee
Beijing Dadao Yunxing Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Dadao Yunxing Technology Co ltd filed Critical Beijing Dadao Yunxing Technology Co ltd
Priority to CN202310070104.9A priority Critical patent/CN115834713A/en
Publication of CN115834713A publication Critical patent/CN115834713A/en
Pending legal-status Critical Current

Links

Images

Abstract

The application discloses an interaction method and system of a network file system and a distributed file system, which comprises the steps of obtaining a client request; processing the client request by using the coroutine to obtain a network file task; calling a corresponding composite request interface function according to the network file task type to generate a distributed file task; processing the distributed file task to obtain a request result; and returning the request result to the network file system; after receiving a client request, the client request is processed and converted into a network file task by using a coroutine so as to reduce resource consumption and concurrency problems of a multithreading model, and a corresponding composite request interface function is called according to the type of the network file task to generate a distributed file task and then process the distributed file task so as to reduce the request times and improve the request processing efficiency.

Description

Interaction method and system for network file system and distributed file system
Technical Field
The application relates to the technical field of interaction of a network file system and a distributed file system, in particular to an interaction method and system of the network file system and the distributed file system.
Background
With the rapid development of technologies such as cloud computing, big data, 5G, AI, etc., unstructured data presentation has exploded growth, including videos, pictures, documents, etc. And the capacity of unstructured data is continuously increasing, and compared with traditional storage, the distributed storage system has the advantages of being high in expansion, high in performance, high in reliability, multi-protocol and the like.
Network File System (NFS) is one of the standard access protocols for enterprise-class File storage systems. And the user state NFS Server has the advantages of more flexibility, easy management, easy debugging, portability and the like, wherein the open source software NFS-Ganesha is a more common user state NFS Server, provides a File System Abstraction Layer (FSAL), and can be connected with different File systems. In the prior art, NFS-Ganesha is generally used to match with a Distributed File System (DFS), such as CephFS, glusterFS, GPFS, lustre, or the like, to provide network File storage and sharing services to the outside.
Generally, NFS-Ganesha uses a multithread model to process requests, and for each NFS client request, after being processed by an RPC layer, an NFS protocol layer, and the like, a worker thread finally processes the NFS client request, and the worker thread calls a client API of a specific back-end file system (such as CephFS) through an FSAL layer to interact with the back-end file system, so as to complete the request operation. However, in a data intensive scenario, NFS-Ganesha occupies a large number of threads, and a large number of threads are created and switched, which causes much resource consumption and time overhead; meanwhile, the synchronization among multiple threads needs a locking mechanism, so that the concurrency can be reduced, and the performance of back-end storage and high-speed hardware is not favorably exerted; in addition, the interaction interface between the NFS Server and its backend file system is not specially designed for the distributed file system, and there is an additional performance loss due to the increased number of interactions when processing requests.
Disclosure of Invention
The present application is proposed to solve the above-mentioned technical problems. The embodiment of the application provides an interaction method and system of a network file system and a distributed file system, and solves the technical problem.
According to an aspect of the present application, there is provided an interactive method of a network file system and a distributed file system, including: acquiring a client request; processing the client request by using a coroutine to obtain a network file task; calling a corresponding composite request interface function according to the network file task type to generate a distributed file task; processing the distributed file task to obtain a request result; and returning the request result to the network file system.
In an embodiment, the invoking a corresponding compound request interface function according to the network file task type to generate a distributed file task includes: polling a task queue to process the network file task in the coroutine; and calling a corresponding composite request interface function according to the network file task type to generate the distributed file task.
In one embodiment, the invoking the corresponding compound request interface function to generate a distributed file task includes: and calling the corresponding composite request interface function to generate a distributed file task to be placed in the distributed file task queue.
In an embodiment, the processing the distributed file task to obtain a request result includes: processing the distributed file task to obtain a request result; and generating a result task according to the request result.
In one embodiment, said returning said request result to said network file system comprises: converting the result task into a network file task; and processing the network file task by adopting the coroutine so as to return the request result to the network file system.
In an embodiment, before the obtaining the client request, the method for interacting the network file system with the distributed file system further includes: and initializing the network file system and the distributed file system.
In an embodiment, the initializing the network file system and the distributed file system includes: starting the distributed file system; analyzing the configuration file of the distributed file system; initializing the distributed file system according to the configuration file; and transmitting the configuration file into the network file system to initialize the network file system.
In an embodiment, the initializing the network file system and the distributed file system includes: and returning the initialization result of the network file system to the distributed file system to complete the initialization of the distributed file system.
According to another aspect of the present application, there is provided an interactive system of a network file system and a distributed file system, comprising: network file systems and distributed file systems; the network file system is used for acquiring a client request, processing the client request by adopting a coroutine to obtain a network file task, and calling a corresponding composite request interface function according to the type of the network file task to generate a distributed file task; the distributed file system is used for processing the distributed file task to obtain a request result and returning the request result to the network file system.
In an embodiment, the network file system includes a network file service front-end module and a network file service back-end module, wherein the network file service front-end module is configured to obtain a client request and process the client request by using a coroutine to obtain a network file task, and the network file service back-end module is configured to call a corresponding composite request interface function according to the network file task type to generate a distributed file task; the distributed file system comprises a distributed file service front-end module and a distributed file service back-end module, wherein the distributed file service front-end module is used for receiving the distributed file task and generating a new task to be placed in a task queue of the distributed file service back-end module, and the distributed file service back-end module is used for processing the new task to obtain a request result and placing the request result in the task queue of the distributed file service front-end module to return to the network file system.
According to the method and the system for interacting the network file system and the distributed file system, the client request is obtained; processing the client request by using the coroutine to obtain a network file task; calling a corresponding composite request interface function according to the network file task type to generate a distributed file task; processing the distributed file task to obtain a request result; and returning the request result to the network file system; after receiving a client request, the client request is processed and converted into a network file task by using a coroutine so as to reduce resource consumption and concurrency problems of a multithreading model, and a corresponding composite request interface function is called according to the type of the network file task to generate a distributed file task and then process the distributed file task so as to reduce the request times and improve the request processing efficiency.
Drawings
The above and other objects, features and advantages of the present application will become more apparent by describing in more detail embodiments of the present application with reference to the attached drawings. The accompanying drawings are included to provide a further understanding of the embodiments of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the principles of the application. In the drawings, like reference numbers generally represent like parts or steps.
Fig. 1 is a flowchart illustrating an interaction method between a network file system and a distributed file system according to an exemplary embodiment of the present application.
Fig. 2 is a flowchart illustrating an interaction method between a network file system and a distributed file system according to another exemplary embodiment of the present application.
Fig. 3 is a flowchart illustrating an initialization method for a network file system and a distributed file system according to an exemplary embodiment of the present application.
Fig. 4 is a flowchart illustrating an initialization method for a network file system and a distributed file system according to another exemplary embodiment of the present application.
Fig. 5 is a schematic structural diagram of an interactive system of a network file system and a distributed file system according to an exemplary embodiment of the present application.
Fig. 6 is a schematic structural diagram of an interactive system of a network file system and a distributed file system according to another exemplary embodiment of the present application.
Fig. 7 is a block diagram of an electronic device provided in an exemplary embodiment of the present application.
Detailed Description
Hereinafter, example embodiments according to the present application will be described in detail with reference to the accompanying drawings. It should be understood that the described embodiments are only some embodiments of the present application and not all embodiments of the present application, and that the present application is not limited by the example embodiments described herein.
Fig. 1 is a flowchart illustrating an interaction method between a network file system and a distributed file system according to an exemplary embodiment of the present application. As shown in fig. 1, the method for interacting the network file system and the distributed file system includes the following steps:
step 110: a client request is obtained.
When a client request is sent from a client of a network file system, the client request is received.
Step 120: and processing the client request by using the coroutine to obtain a network file task.
And processing the received client request in the coroutine, generating a network file task after processing, and putting the network file task into a task queue for further processing.
Step 130: and calling the corresponding composite request interface function according to the network file task type to generate a distributed file task.
In an embodiment, a specific implementation manner of the step 130 may be: polling the task queue to process the network file task in the coroutine; and calling the corresponding composite request interface function according to the network file task type to generate a distributed file task.
In an embodiment, a specific implementation manner of the step 130 may be: and calling the corresponding composite request interface function to generate a distributed file task to be placed in a distributed file task queue. And converting the client request into a corresponding distributed file task by using a composite request interface function, and putting the distributed file task into a task queue of the distributed file system for waiting processing.
Step 140: and processing the distributed file task to obtain a request result.
In an embodiment, the specific implementation manner of step 140 may be: processing the distributed file task to obtain a request result; and generating a result task according to the request result. And processing the distributed file tasks in the task list to obtain corresponding request results, and generating a task to return to the network file system according to the request results.
Step 150: and returning the request result to the network file system.
In an embodiment, the specific implementation manner of step 150 may be: and converting the result task into a network file task, and processing the network file task by using a coroutine to return the request result to the network file system. And after converting a request result requested by a client into a result task, converting the result task into a network file task, placing the network file task in a task queue of a network file system, switching to a corresponding coroutine to process the network file task, and returning a response result to the client.
According to the method for interacting the network file system and the distributed file system, the client request is obtained; processing the client request by using the coroutine to obtain a network file task; calling a corresponding composite request interface function according to the network file task type to generate a distributed file task; processing the distributed file task to obtain a request result; and returning the request result to the network file system; after receiving a client request, the client request is processed and converted into a network file task by using a coroutine so as to reduce resource consumption and concurrency problems of a multithreading model, and a corresponding composite request interface function is called according to the type of the network file task to generate a distributed file task and then process the distributed file task so as to reduce the request times and improve the request processing efficiency.
Fig. 2 is a flowchart illustrating an interaction method between a network file system and a distributed file system according to another exemplary embodiment of the present application. As shown in fig. 2, before step 110, the method for interacting the network file system with the distributed file system may further include:
step 160: and initializing the network file system and the distributed file system.
Before the interaction between the network file system and the distributed file system is started, the network file system and the distributed file system need to be initialized to be matched with each other, so that the interaction can be better realized.
Fig. 3 is a flowchart illustrating an initialization method for a network file system and a distributed file system according to an exemplary embodiment of the present application. As shown in fig. 3, the step 160 may include:
step 161: the distributed file system is started.
Step 162: and analyzing the configuration file of the distributed file system.
First, a Distributed File System (DFS) is started and the configuration file of the DFS is parsed to obtain the required information of CPU, network, port, etc.
Step 163: the distributed file system is initialized according to the configuration file.
According to the configuration information (content of the configuration file) of the distributed file system, initializing each internal component of the distributed file system, and generating a service thread corresponding to each module and required related resources.
Step 164: and transmitting the configuration file into the network file system to initialize the network file system.
Starting a network file system (NFS Server) in a user mode by a distributed file system, transmitting configuration information required by the NFS Server into the NFS Server in a parameter calling mode, wherein the configuration information required by the NFS Server comprises a CPU (central processing unit), a network and a handle during DFS (distributed file system) operation, a composite request interface function pointer and the like required by the NFS Server, and initializing each module in the NFS Server according to the configuration information.
In an embodiment, as shown in fig. 3, the step 160 may further include:
step 165: and returning the initialization result of the network file system to the distributed file system so as to finish the initialization of the distributed file system.
Specifically, after the NFS Server is initialized, the handle information list and the compound request interface function pointer list during the DFS operation are registered in the compound request processing layer, and the DFS initialization is completed.
Fig. 4 is a flowchart illustrating an initialization method for a network file system and a distributed file system according to another exemplary embodiment of the present application. As shown in fig. 4, the initialization method includes the steps of:
step 410: the distributed file system is started.
The specific implementation manner of step 410 is as described in step 161 of the above embodiment, and is not described herein again.
Step 420: and reading and analyzing the configuration file to obtain the information of the required CPU, network and port.
The specific implementation manner of step 420 is as described in step 162 of the above embodiment, and is not described herein again.
Step 430: and initializing each module of the DFS according to the configuration information, and generating a service thread corresponding to each module and required related resources.
The specific implementation manner of step 430 is as described in step 163 of the above embodiment, and is not described herein again.
Step 440: and calling a Server interface to start the NFS Server, and transmitting the information of the handles and the function pointers of the composite request interface when the Server interface runs in the CPU, the network and the DFS.
The specific implementation of step 440 is as described in step 164 of the above embodiment, and is not described herein again.
Step 450: the NFS Server initializes each module according to the incoming information, generates a service thread corresponding to each module and required related resources, and registers the incoming function pointer and runtime handle to the composite request processing layer.
The specific implementation manner of step 450 is as described in step 164 of the above embodiment, and is not described herein again.
Step 460: and after the initialization of the NFS Server is completed, returning the result to the DFS.
The specific implementation of step 460 is as described in step 165 of the above embodiment, and is not described here again.
Step 470: the DFS initialization is complete.
The specific implementation manner of step 470 is as described in step 165 of the above embodiment, and is not described here again.
Fig. 5 is a schematic structural diagram of an interactive system of a network file system and a distributed file system according to an exemplary embodiment of the present application. As shown in fig. 5, the interactive system includes: a network file system 1 and a distributed file system 2; the network file system 1 is used for acquiring a client request, processing the client request by using a coroutine to obtain a network file task, and calling a corresponding composite request interface function according to the type of the network file task to generate a distributed file task; the distributed file system 2 is used for processing the distributed file task to obtain a request result and returning the request result to the network file system.
According to the interactive system of the network file system and the distributed file system, the client request is obtained; processing the client request by using the coroutine to obtain a network file task; calling a corresponding composite request interface function according to the network file task type to generate a distributed file task; processing the distributed file task to obtain a request result; and returning the request result to the network file system; after receiving a client request, the client request is processed and converted into a network file task by using a coroutine so as to reduce resource consumption and concurrency problems of a multithreading model, and a corresponding composite request interface function is called according to the type of the network file task to generate a distributed file task and then process the distributed file task so as to reduce the request times and improve the request processing efficiency.
Fig. 6 is a schematic structural diagram of an interactive system of a network file system and a distributed file system according to another exemplary embodiment of the present application. As shown in fig. 6, the network file system 1 may include a network file service front-end module 11 and a network file service back-end module 12, where the network file service front-end module 11 is configured to obtain a client request and process the client request by using a coroutine to obtain a network file task, and the network file service back-end module 12 is configured to call a corresponding composite request interface function according to a network file task type to generate a distributed file task; the distributed file system 2 may include a distributed file service front-end module 21 and a distributed file service back-end module 22, where the distributed file service front-end module 21 is configured to receive a distributed file task and generate a new task to be placed in a task queue of the distributed file service back-end module 22, and the distributed file service back-end module 22 is configured to process the new task to obtain a request result, and place the request result in the task queue of the distributed file service front-end module 21 to return to the network file system 1.
The specific implementation manner of the interactive system is as follows:
(1) The NFS client sends a client request to the network file service front-end module 11.
(2) The network file service front-end module 11 receives and processes in the coroutine, generates a new task and puts the new task into a task queue of the network file service back-end module 12, and the network file service front-end module 11 asynchronously receives the response.
(3) The network file service back-end module 12 polls the task queue, performs task processing in the coroutine, calls a corresponding composite request interface function according to the task type, and the network file service back-end module 12 asynchronously receives a response.
(4) The composite request interface converts the request into a corresponding distributed file task, and puts the distributed file task into a task queue of the distributed file service front-end module 21, and then the composite request interface function completes the return.
(5) The distributed file service front-end module 21 polls the task queue, further processes the request in the coroutine and generates a new task, and puts the new task into the task queue of the distributed file service back-end module 22, and the distributed file service front-end module 21 asynchronously receives the response.
(6) The distributed file service back-end module 22 polls the task queue, processes the request, and after the processing is completed, generates a task according to the processing result and puts the task into a response correspondence of the distributed file service front-end module 21.
(7) The distributed file service front-end module 21 polls the response queue, switches to the corresponding coroutine for processing according to the response information, and puts the processing result into the response queue of the network file service back-end module 12.
(8) The network file service back-end module 12 polls the response queue, switches to the corresponding coroutine for processing according to the response information, and puts the processing result into the response queue of the network file service front-end module 11.
(9) The network file service front-end module 11 polls the response queue, switches to corresponding coroutine processing according to the response information, and returns a response to the NFS client.
Next, an electronic apparatus according to an embodiment of the present application is described with reference to fig. 7. The electronic device may be either or both of the first device and the second device, or a stand-alone device separate from them, which stand-alone device may communicate with the first device and the second device to receive the acquired input signals therefrom.
FIG. 7 illustrates a block diagram of an electronic device in accordance with an embodiment of the application.
As shown in fig. 7, the electronic device 10 includes one or more processors 11 and memory 12.
The processor 11 may be a Central Processing Unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device 10 to perform desired functions.
Memory 12 may include one or more computer program products that may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, random Access Memory (RAM), cache memory (cache), and/or the like. The non-volatile memory may include, for example, read Only Memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium and executed by processor 11 to implement the methods of the various embodiments of the present application described above and/or other desired functions. Various contents such as an input signal, a signal component, a noise component, etc. may also be stored in the computer-readable storage medium.
In one example, the electronic device 10 may further include: an input device 13 and an output device 14, which are interconnected by a bus system and/or other form of connection mechanism (not shown).
When the electronic device is a stand-alone device, the input means 13 may be a communication network connector for receiving the acquired input signals from the first device and the second device.
The input device 13 may also include, for example, a keyboard, a mouse, and the like.
The output device 14 may output various information including the determined distance information, direction information, and the like to the outside. The output devices 14 may include, for example, a display, speakers, a printer, and a communication network and its connected remote output devices, among others.
Of course, for simplicity, only some of the components of the electronic device 10 relevant to the present application are shown in fig. 7, and components such as buses, input/output interfaces, and the like are omitted. In addition, the electronic device 10 may include any other suitable components depending on the particular application.
The computer program product may be written with program code for performing the operations of embodiments of the present application in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server.
The computer-readable storage medium may take any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The foregoing description has been presented for purposes of illustration and description. Furthermore, the description is not intended to limit embodiments of the application to the form disclosed herein. While a number of example aspects and embodiments have been discussed above, those of skill in the art will recognize certain variations, modifications, alterations, additions and sub-combinations thereof.

Claims (10)

1. An interactive method of a network file system and a distributed file system is characterized by comprising the following steps:
acquiring a client request;
processing the client request by using a coroutine to obtain a network file task;
calling a corresponding composite request interface function according to the network file task type to generate a distributed file task;
processing the distributed file task to obtain a request result; and
and returning the request result to the network file system.
2. The method of claim 1, wherein the invoking a corresponding compound request interface function according to the network file task type to generate a distributed file task comprises:
polling a task queue to process the network file task in the coroutine; and
and calling a corresponding composite request interface function according to the network file task type to generate the distributed file task.
3. The method of claim 1, wherein the invoking of the corresponding compound request interface function to generate a distributed file task comprises:
and calling a corresponding composite request interface function to generate a distributed file task to be placed in the distributed file task queue.
4. The method of claim 1, wherein the processing the distributed file task to obtain the request result comprises:
processing the distributed file task to obtain a request result; and
and generating a result task according to the request result.
5. The method of claim 4, wherein the returning the request result to the network file system comprises:
converting the result task into a network file task; and
and processing the network file task by adopting the coroutine so as to return the request result to the network file system.
6. The method of claim 1, wherein prior to the obtaining the client request, the method further comprises:
and initializing the network file system and the distributed file system.
7. The method of claim 6, wherein initializing the network file system and the distributed file system comprises:
starting the distributed file system;
analyzing the configuration file of the distributed file system;
initializing the distributed file system according to the configuration file;
and transmitting the configuration file into the network file system to initialize the network file system.
8. The method of claim 7, wherein initializing the network file system and the distributed file system comprises:
and returning the initialization result of the network file system to the distributed file system to complete the initialization of the distributed file system.
9. An interactive system of a network file system and a distributed file system, comprising: network file systems and distributed file systems;
the network file system is used for acquiring a client request, processing the client request by adopting a coroutine to obtain a network file task, and calling a corresponding composite request interface function according to the type of the network file task to generate a distributed file task;
the distributed file system is used for processing the distributed file task to obtain a request result and returning the request result to the network file system.
10. The system according to claim 9, wherein the network file system comprises a network file service front-end module and a network file service back-end module, wherein the network file service front-end module is configured to obtain a client request and process the client request by using a coroutine to obtain a network file task, and the network file service back-end module is configured to call a corresponding composite request interface function according to the network file task type to generate a distributed file task;
the distributed file system comprises a distributed file service front-end module and a distributed file service back-end module, wherein the distributed file service front-end module is used for receiving the distributed file task and generating a new task to be placed in a task queue of the distributed file service back-end module, and the distributed file service back-end module is used for processing the new task to obtain a request result and placing the request result in the task queue of the distributed file service front-end module to return to the network file system.
CN202310070104.9A 2023-02-07 2023-02-07 Interaction method and system for network file system and distributed file system Pending CN115834713A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310070104.9A CN115834713A (en) 2023-02-07 2023-02-07 Interaction method and system for network file system and distributed file system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310070104.9A CN115834713A (en) 2023-02-07 2023-02-07 Interaction method and system for network file system and distributed file system

Publications (1)

Publication Number Publication Date
CN115834713A true CN115834713A (en) 2023-03-21

Family

ID=85520856

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310070104.9A Pending CN115834713A (en) 2023-02-07 2023-02-07 Interaction method and system for network file system and distributed file system

Country Status (1)

Country Link
CN (1) CN115834713A (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1121216A (en) * 1994-03-07 1996-04-24 国际商业机器公司 System and method for efficient caching in a distributed file system
US5710918A (en) * 1995-06-07 1998-01-20 International Business Machines Corporation Method for distributed task fulfillment of web browser requests
CN101944124A (en) * 2010-09-21 2011-01-12 卓望数码技术(深圳)有限公司 Distributed file system management method, device and corresponding file system
CN104408088A (en) * 2014-11-11 2015-03-11 北京奇虎科技有限公司 Control method and device for concurrent requests
CN108123820A (en) * 2016-11-29 2018-06-05 北京神州泰岳软件股份有限公司 A kind of network equipment information acquisition method and device
CN109740381A (en) * 2019-01-08 2019-05-10 郑州云海信息技术有限公司 A kind of authority control method across file system, device, equipment and storage medium
CN111741080A (en) * 2020-06-02 2020-10-02 拉卡拉支付股份有限公司 Network file distribution method and device
CN112653730A (en) * 2020-12-10 2021-04-13 苏州浪潮智能科技有限公司 User mode network file storage method and system

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1121216A (en) * 1994-03-07 1996-04-24 国际商业机器公司 System and method for efficient caching in a distributed file system
US5710918A (en) * 1995-06-07 1998-01-20 International Business Machines Corporation Method for distributed task fulfillment of web browser requests
CN101944124A (en) * 2010-09-21 2011-01-12 卓望数码技术(深圳)有限公司 Distributed file system management method, device and corresponding file system
CN104408088A (en) * 2014-11-11 2015-03-11 北京奇虎科技有限公司 Control method and device for concurrent requests
CN108123820A (en) * 2016-11-29 2018-06-05 北京神州泰岳软件股份有限公司 A kind of network equipment information acquisition method and device
CN109740381A (en) * 2019-01-08 2019-05-10 郑州云海信息技术有限公司 A kind of authority control method across file system, device, equipment and storage medium
CN111741080A (en) * 2020-06-02 2020-10-02 拉卡拉支付股份有限公司 Network file distribution method and device
CN112653730A (en) * 2020-12-10 2021-04-13 苏州浪潮智能科技有限公司 User mode network file storage method and system

Similar Documents

Publication Publication Date Title
JP7194162B2 (en) Data processing method, device, electronic device and storage medium
US20200099606A1 (en) Distrubuted testing service
CN109213611B (en) Cross-process communication method, device, terminal and storage medium
US7673029B2 (en) Grid automation bus to integrate management frameworks for dynamic grid management
US5452459A (en) Method and apparatus for allocating server access in a distributed computing environment
CN110489440B (en) Data query method and device
CN107493266B (en) Communication system, method and device of embedded self-service terminal
CN109831466B (en) Micro-service business processing method and nginx server
US11150817B2 (en) Integrating kernel-bypass user-level file systems into legacy applications
CN111679911B (en) Management method, device, equipment and medium of GPU card in cloud environment
US11321090B2 (en) Serializing and/or deserializing programs with serializable state
CN111737022A (en) Interface calling method, system, equipment and medium based on micro-service
CN111400000A (en) Network request processing method, device, equipment and storage medium
CN110851276A (en) Service request processing method, device, server and storage medium
KR20090123012A (en) Distributed processing system and method
CN110781159B (en) Ceph directory file information reading method and device, server and storage medium
US9473565B2 (en) Data transmission for transaction processing in a networked environment
KR102314221B1 (en) Virtual desktop system providing an environment at specific time and method thereof
US7080387B2 (en) System and method for mediating communication between software applications
CN109240995B (en) Method and device for counting time delay of operation word
CN115834713A (en) Interaction method and system for network file system and distributed file system
CN115237481A (en) Method, device and equipment for driving external equipment and storage medium
KR101361838B1 (en) Method for accelerating virtual desktop protocol based on server virtualization and virtualization server for performing the same
CN113625998A (en) Request processing method and device
US11340949B2 (en) Method and node for managing a request for hardware acceleration by means of an accelerator device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20230321