WO2024037222A1 - 文件系统的管理方法及装置 - Google Patents

文件系统的管理方法及装置 Download PDF

Info

Publication number
WO2024037222A1
WO2024037222A1 PCT/CN2023/104514 CN2023104514W WO2024037222A1 WO 2024037222 A1 WO2024037222 A1 WO 2024037222A1 CN 2023104514 W CN2023104514 W CN 2023104514W WO 2024037222 A1 WO2024037222 A1 WO 2024037222A1
Authority
WO
WIPO (PCT)
Prior art keywords
target object
file system
access
access consistency
consistency
Prior art date
Application number
PCT/CN2023/104514
Other languages
English (en)
French (fr)
Inventor
金瑜
方新
谢晓芹
Original Assignee
华为云计算技术有限公司
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
Priority claimed from CN202211406915.3A external-priority patent/CN117632849A/zh
Application filed by 华为云计算技术有限公司 filed Critical 华为云计算技术有限公司
Publication of WO2024037222A1 publication Critical patent/WO2024037222A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/13—File access structures, e.g. distributed indices

Definitions

  • the present application relates to the technical field of file systems, and in particular to a file system management method and device.
  • File systems such as distributed file systems (DFS)
  • DFS distributed file systems
  • FFS distributed file systems
  • file systems are mainstream storage systems that integrate high reliability, high scalability, and high performance. They are currently widely used in scenarios such as media assets, high-end computing, and genetics.
  • different application scenarios put forward different application requirements for the access consistency of the file system.
  • the access consistency requirement in the gap between different clients accessing the same content of the file system, the data obtained by different clients accessing the content must be exactly the same, provided that the content is not modified.
  • the access consistency level of the file system is determined, which is difficult to apply to different application scenarios with different application requirements, resulting in poor usability of the file system.
  • This application provides a file system management method and device. This application allows the access consistency of the file system to be changed after the design is completed, so that the access consistency of the file system objects can be easily adjusted according to different application requirements.
  • the technical solutions provided by this application are as follows:
  • this application provides a file system management method.
  • the method includes: receiving an operation instruction when the file system is in a usable state, and the operation instruction indicates operating on the access consistency of a target object of the file system; based on the operation instruction, performing an operation indicated by the operation instruction on the target object.
  • the computer device when the file system is in a usable state, the computer device can receive the operation instruction sent by the first client, and based on the operation instruction, perform the operation indicated by the operation instruction on the target object. .
  • the operation instruction indicates operating on the access consistency of the target object of the file system. Since when the file system is in a usable state, the computer device can operate on the access consistency of the target object of the file system based on the operation instructions, so that the access consistency of the file system can be changed after the design is completed. , which makes it easy to adjust the access consistency of file system objects according to different application requirements, so that the file system can meet the application requirements of different application scenarios, and effectively improves the usability of the file system.
  • the target object includes one or more of the following: the root directory of the file system, the directory and the file.
  • the computer device can perform corresponding access consistency operations on the target object according to the operation instructions, different target objects in the file system can be configured to have different access consistency. In this way, the same file system can support multiple access consistency in parallel, further improving the flexibility of the file system and the availability of the file system.
  • the operation includes one or more of the following: configuring the access consistency of the target object; modifying the access consistency of the target object; and querying the access consistency of the target object.
  • configuring the access consistency of the target object includes one or more of the following: configuring the access consistency of the target object, and configuring the target object's subordinate objects to inherit the target object configuration Access consistency; configure the access consistency of the target object, and the subordinate objects of the configured target object do not inherit the access consistency configured for the target object.
  • modifying the access consistency of the target object includes one or more of the following: modifying the access consistency of the target object, and configuring the subordinate objects of the target object to inherit the modified access consistency of the target object. Access consistency; and, modify the access consistency of the target object, and configure the subordinate objects of the target object not to inherit the modified access consistency of the target object.
  • the configurability of the access consistency of objects in the file system is enriched at a finer granularity, which can better satisfy users' access to objects in the file system. Consistency appeal.
  • access consistency includes one or more of the following: after performing a write operation on the target object, a read operation on the target object can read the data after the write operation; after performing a write operation on the target object, operation, and after the target object is refreshed, the read operation on the target object can read the data after the write operation is performed; after the write operation is performed on the target object and the target object is restarted, the read operation on the target object can read to the data after performing the write operation.
  • the method after performing the operation indicated by the operation instruction on the target object based on the operation instruction, the method also includes: receiving an access instruction, which indicates access to the target object; based on the access consistency of the target object, according to the access consistency of the target object. The state after executing the operation indicated by the operation instruction and responding to the access instruction.
  • this application provides a file system management device.
  • the management device of the file system includes: an interaction module, used to receive operation instructions when the file system is in a usable state, and the operation instructions indicate operations based on the access consistency of target objects of the file system; a processing module, based on Operation instructions: perform the operations indicated by the operation instructions on the target object.
  • the target object includes one or more of the following: root directory, directory, and file of the file system.
  • different target objects in the file system can be configured to have different access consistency.
  • the operation includes one or more of the following: configuring the access consistency of the target object; modifying the access consistency of the target object; and querying the access consistency of the target object.
  • configuring the access consistency of the target object includes one or more of the following: configuring the access consistency of the target object, and configuring the target object's subordinate objects to inherit the target object configuration Access consistency; configure the access consistency of the target object, and the subordinate objects of the configured target object do not inherit the access consistency configured for the target object.
  • modifying the access consistency of the target object includes one or more of the following: modifying the access consistency of the target object, and configuring the subordinate objects of the target object to inherit the modified access consistency of the target object. Access consistency; and, modify the access consistency of the target object, and configure the subordinate objects of the target object not to inherit the modified access consistency of the target object.
  • access consistency includes one or more of the following: after a write operation is performed on the target object, a read operation on the target object can read the data after the write operation is performed; after a write operation is performed on the target object, and After the target object is refreshed, the read operation on the target object can read the data after the write operation is performed; after the write operation is performed on the target object and the target object is restarted, the read operation on the target object can read the data after the write operation is performed. Data after operation.
  • the interaction module is also used to receive access instructions, which indicate access to the target object; the processing module is also used to determine the state of the target object after performing the operations indicated by the operation instructions based on the access consistency of the target object. , respond to access instructions.
  • this application provides a computer device, including a memory and a processor.
  • the memory stores program instructions
  • the processor runs the program instructions to execute the method provided in the first aspect of this application and any possible implementation thereof. .
  • this application provides a computer cluster, including multiple computer devices.
  • the multiple computer devices include multiple processors and multiple memories.
  • Program instructions are stored in the multiple memories, and the multiple processors run the program instructions.
  • the computer cluster is caused to execute the method provided in the first aspect of this application and any possible implementation manner thereof.
  • the application provides a computer-readable storage medium.
  • the computer-readable storage medium is a non-volatile computer-readable storage medium.
  • the computer-readable storage medium includes program instructions. When the program instructions are stored on a computer device, When running, the computer device is caused to execute the method provided in the first aspect of the application and any possible implementation manner thereof.
  • this application provides a computer program product containing instructions.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the method provided in the first aspect of this application and any possible implementation thereof.
  • Figure 1 is a schematic diagram of a file system provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of the implementation environment involved in a file system management method provided by an embodiment of the present application
  • Figure 3 is a schematic diagram of the implementation environment involved in another file system management method provided by the embodiment of the present application.
  • Figure 4 is a flow chart of a file system management method provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of an access consistency operation provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of another access consistency operation provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of another access consistency operation provided by an embodiment of the present application.
  • Figure 8 is a schematic diagram of a file system management device provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a computer device provided by an embodiment of the present application.
  • a file system is a method and data structure used by the operating system to identify files on storage devices (such as disks, solid-state drives, etc.) or partitions, and is used to manage and store file information of files.
  • the file system is a system that organizes and allocates the space of file storage devices, is responsible for file storage, and protects and retrieves stored files.
  • the file system is responsible for creating files for users, saving files, reading file data, modifying file data, transferring files, controlling file access, and revoking files when users no longer use them.
  • the file system consists of three parts: the file system interface, the software collection for object manipulation and management, and the file system objects.
  • the objects of the file system include: root directory (ROOT), directory (directory) and file (file).
  • the relationship between the file system and its objects can be represented by a tree structure, as shown in Figure 1.
  • the file system includes root directories, directories and files.
  • the subordinate objects of the root directory can include directory 1, file 1, etc., the subordinate objects of directory 1 include directory 2, file 2, etc., and so on.
  • File systems (such as distributed file systems) are mainstream storage systems that integrate high reliability, high scalability, and high performance. They are currently widely used in scenarios such as media assets, high-end computing, and genetics. Moreover, different application scenarios have different application requirements for file system access consistency. Among them, the access consistency requirement: in the gap between different clients accessing the same content of the file system, the data obtained by different clients accessing the content must be exactly the same, provided that the content is not modified.
  • the access consistency level of the file system is determined, and the file system can only work according to its determined access consistency.
  • the file system only supports one access consistency, causing all directories and files in the file system to work only according to this access consistency. Therefore, the current file system is difficult to apply to different application scenarios with different application requirements, resulting in poor usability of the file system.
  • Embodiments of the present application provide a file system management method and device.
  • the computer device when the file system is in a usable state, the computer device can receive the operation instruction sent by the first client, and based on the operation instruction, perform the operation indicated by the operation instruction on the target object.
  • the operation instruction indicates operating on the access consistency of the target object of the file system.
  • the computer device can operate on the access consistency of the target object of the file system based on the operation instructions, so that the access consistency of the file system can be changed after the design is completed. , which makes it easy to adjust the access consistency of file system objects according to different application requirements, so that the file system can meet the application requirements of different application scenarios, and effectively improves the usability of the file system.
  • FIG. 2 is a schematic structural diagram of an implementation environment involved in a file system management method provided by an embodiment of the present application.
  • the implementation environment includes: a computer device 10.
  • the computer device 10 can run a file system, and users can use the file system to manage their files. Furthermore, when the user needs to perform an operation on the access consistency of the object of the file system, he or she can send an operation instruction to the computer device 10 to instruct the computer device 10 to perform the operation on the access consistency of the target object of the file system. After receiving the operation instruction, the computer device 10 can perform the operation indicated by the operation instruction on the target object based on the operation instruction, so that after receiving the access instruction indicating access to the target object, the computer device 10 can access the target object according to the operation instruction. The state after executing the operation indicated by the operation instruction and responding to the access instruction.
  • the file system management method provided by the embodiment of the present application can be implemented by running an executable program on the computer device 10 .
  • the executable program of the file system management method may be presented in the form of an application installation package. After the application installation package is installed in the computer device 10 , the file system management method can be implemented by running the executable program.
  • the computer device 10 may be a terminal.
  • the terminal may be a computer, a personal computer, a portable mobile terminal, a multimedia player, an e-book reader or a wearable device, etc.
  • the implementation environment may include a computer device 10 and a client 20 .
  • Client 20 is able to A communication connection is established with the computer device 10 .
  • a communication connection may be established between the client 20 and the computer device 10 through a network.
  • the network may be a local area network, the Internet, or other networks, which are not limited in the embodiments of this application.
  • the user can interact with the computer device 10 through the client 20 .
  • the user can send instructions such as operation instructions and access instructions to the computer device 10 through the client 20 .
  • the computer device 10 is configured to run a file system, manage the user's files through the file system, and respond according to the instructions after receiving instructions sent by the client 20 .
  • the computer device 10 can operate on the access consistency of the target object of the file system according to the instructions of the operation instruction.
  • the computer device 10 may respond based on the access instruction.
  • the client 20 can be a computer, a personal computer, a laptop, a mobile phone, a smart phone, a tablet, a cloud host, a portable mobile terminal, a multimedia player, an e-book reader, a wearable Equipment, smart home appliances, artificial intelligence equipment, smart wearable devices, smart vehicle equipment or Internet of Things equipment, etc.
  • Computer device 10 may be a server.
  • the server can be one server, or a server cluster composed of several servers, or a cloud computing service center.
  • a large number of basic resources owned by cloud service providers are deployed in the cloud computing service center. For example, computing resources, storage resources, network resources, etc. are deployed in a cloud computing service center.
  • the cloud computing service center can utilize this large amount of basic resources to run the file system and implement the file system management method provided by the embodiments of this application.
  • the server When the server is implemented through a cloud computing service center.
  • the user can access the cloud platform through the client 20 and use the file system through the cloud platform.
  • the server provides users with the function of a file system and a file system management method, which can be abstracted into a file system cloud service by the cloud service provider on the cloud platform.
  • the cloud platform can use the resources in the cloud computing center to provide the file system to the user, and manage the file system using the file system management method provided by the embodiment of the present application.
  • the cloud platform may be a central cloud cloud platform, an edge cloud cloud platform, or a cloud platform including a central cloud and an edge cloud, which are not specifically limited in the embodiments of this application.
  • the computer device 10 can also be implemented through other resource platforms besides the cloud platform, which is not specifically limited in the embodiments of this application.
  • the server can be implemented through resources in other resource platforms and provide file system-related services to users.
  • the management method of this file system includes the following steps:
  • Step 401 When the file system is in a usable state, receive an operation instruction, and the operation instruction instructs to operate on the access consistency of the target object of the file system.
  • the user can trigger an operation instruction through some operations, so that the computer device can operate the access consistency of the target object of the file system based on the operation instruction.
  • Perform operations For example, when a user is using the file system cloud service provided by the cloud platform and determines based on his or her business requirements that operations need to be performed on the access consistency of the target object of the file system, the user can trigger the client to report to the cloud platform by performing some operations.
  • the operation instruction is sent so that the cloud platform can operate on the access consistency of the target object of the file system based on the operation instruction.
  • the fact that the file system is in a usable state means that the design of the file system has been completed.
  • the target object of the file system includes one or more of the following: granular components such as the root directory of the file system, directories, and files. Among them, operating on the root directory of the file is operating on the entire file system. Moreover, the files in the file system can be files subordinate to the root directory or files subordinate to the directory. It should be noted that when the file system has components of other granularities, the target object can also be of other granularities. Moreover, when the target object is a granular component such as the root directory, directory, and file of the file system, by operating on the access consistency of the component of the corresponding granularity, the consistency of the component of the granularity can be targeted for different users. demands, provides different levels of access consistency, and can provide users with a more flexible file system.
  • granular components such as the root directory of the file system, directories, and files.
  • operating on the root directory of the file is operating on the entire file system.
  • the files in the file system can be files subordinate to the root
  • the operations that can be performed on the target object include one or more of the following: configuring the access consistency of the target object, modifying the access consistency of the target object, and querying the access consistency of the target object.
  • This configuration operation is used to configure the access consistency of the target object when creating the target object.
  • This modification operation is used to modify the target object when the target object has been configured with access consistency. The access consistency of the object is modified.
  • configuring the access consistency of the target object may include: configuring the access consistency of the target object, and configuring the subordinate objects of the target object to inherit the access consistency configured by the target object; configuring the access consistency of the target object, and configuring the target object.
  • the object's subordinate objects do not inherit the access consistency configured for the target object.
  • modifying the access consistency of the target object may include: modifying the access consistency of the target object, and configuring the target object's subordinate objects to inherit the modified access consistency of the target object; modifying the access consistency of the target object, and configuring the target object.
  • the object's subordinate objects do not inherit the modified access consistency of the target object.
  • the target object includes one or more of the following: the root directory, directory and file of the file system
  • the computer device can perform corresponding access consistency operations on the target object according to the operation instructions, so that the file Different target objects in the system can be configured to have different access consistency.
  • the same file system can support multiple access consistency in parallel, further improving the flexibility of the file system and the availability of the file system.
  • the first operation configure the access consistency of the file system.
  • the first implementation situation is to configure the access consistency of the file system, and the subordinate objects of the configuration file system inherit the access consistency of the file system configuration;
  • the second implementation situation is to configure the access consistency of the file system, and the subordinate objects of the configured file system do not inherit the access consistency configured for the file system.
  • the operation instructions can be implemented in different ways.
  • subordinate objects of a file system can inherit the access consistency configured for the file system by default.
  • the operation instructions may or may not carry parameters indicating whether to inherit.
  • the operation command needs to carry parameters indicating whether to inherit it.
  • the operation instruction can be: Set File System Access Consistency Level (FileSystemId, AccessConsistencyLevel), where FileSystemId indicates the file system that needs to be configured with access consistency, and AccessConsistencyLevel indicates the access consistency that needs to be configured for the file system.
  • the operation instruction can be: Set File System Access Consistency Level (FileSystemId, AccessConsistencyLevel, Bool ifSonInheritance), where FileSystemId indicates the file system that needs to be configured with access consistency, AccessConsistencyLevel indicates the access consistency that needs to be configured for the file system, and Bool ifSonInheritance indicates whether the subordinate objects of the file system inherit the access consistency configured for the file system.
  • Bool ifSonInheritance When Bool ifSonInheritance is assigned a value of true, it indicates that the subordinate objects of the file system inherit the access consistency configured for the file system. When the assignment of Bool ifSonInheritance is false , indicates that the file system's subordinate objects do not inherit the access consistency configured for the file system.
  • the operation instruction does not need to carry the FileSystemId, that is, does not indicate the file system.
  • the access consistency of all file systems used by the user who sends the operation instruction can be set according to the operation instruction.
  • parameters that need to be carried by the operation instructions can be set according to application requirements, which are not specifically limited in the embodiments of this application.
  • the second operation Modify the access consistency of the file system.
  • the first implementation situation is to modify the access consistency of the file system, and the subordinate objects of the configuration file system inherit the modified access consistency of the file system; the second implementation situation The second implementation situation is to modify the access consistency of the file system, and the subordinate objects of the configuration file system do not inherit the modified access consistency of the file system.
  • the operation instructions can be implemented in different ways.
  • subordinate objects of a file system can inherit the file system's modified access consistency by default.
  • the operation instructions may or may not carry parameters indicating whether to inherit.
  • the operation instructions need to carry parameters indicating whether to inherit.
  • the operation instruction can be: Modify File System Access Consistency Level (FileSystemId, AccessConsistencyLevel), where FileSystemId indicates the file system whose access consistency needs to be modified, and AccessConsistencyLevel indicates the modified access consistency of the file system.
  • FileSystemId indicates the file system whose access consistency needs to be modified
  • AccessConsistencyLevel indicates the modified access consistency of the file system.
  • the operation instruction can be: Modify File System Access Consistency Level (FileSystemId, AccessConsistencyLevel, Bool ifSonInheritance), where FileSystemId indicates that modification is required Access consistency file system, AccessConsistencyLevel indicates the modified access consistency of the file system, Bool ifSonInheritance indicates whether the subordinate objects of the file system inherit the modified access consistency of the file system, when Bool ifSonInheritance is assigned a value of true, it indicates that the file system Subordinate objects inherit the modified access consistency of the file system. When Bool ifSonInheritance is assigned a value of false, it means that the subordinate objects of the file system do not inherit the modified access consistency of the file system.
  • FileSystemId indicates that modification is required Access consistency file system
  • AccessConsistencyLevel indicates the modified access consistency of the file system
  • Bool ifSonInheritance indicates whether the subordinate objects of the file system inherit the modified access consistency of the file system
  • the operation instruction does not need to carry the FileSystemId, that is, it does not indicate the file system.
  • the access consistency of all file systems used by the user who sends the operation instruction can be modified according to the operation instruction.
  • parameters that need to be carried by the operation instructions can be set according to application requirements, which are not specifically limited in the embodiments of this application.
  • the third operation Query the access consistency of the file system.
  • the operation instruction can be: Get File System Access Consistency Level (FileSystemId), where FileSystemId indicates the file system that needs to be queried.
  • FileSystemId indicates the file system that needs to be queried.
  • the operation instruction does not need to carry the FileSystemId, that is, does not indicate the file system.
  • the access consistency of all file systems used by the user who sends the operation instruction can be queried according to the operation instruction.
  • parameters that need to be carried by the operation instructions can be set according to application requirements, which are not specifically limited in the embodiments of this application.
  • the fourth operation configure the access consistency of the directory.
  • this configuration operation there are two implementations of this configuration operation: the first implementation is to configure the access consistency of the directory, and the subordinate objects of the configuration directory are inherited as the access consistency of the directory configuration; the second implementation is In this case, the access consistency of the directory is configured, and the subordinate objects of the configured directory do not inherit the access consistency configured for the directory.
  • the operation instructions can be implemented in different ways.
  • subordinate objects of a directory can inherit the access consistency configured for the directory by default.
  • the operation instruction may or may not carry a parameter indicating whether to inherit.
  • the operation instruction needs to carry parameters indicating whether to inherit it.
  • the operation instruction can be: Set Dir Access Consistency Level (DirID, AccessConsistencyLevel), where DirID indicates the directory where access consistency needs to be configured, and AccessConsistencyLevel indicates the access consistency that needs to be configured for the directory.
  • the operation instruction can be: Set Dir Access Consistency Level (DirID, AccessConsistencyLevel, Bool ifSonInheritance), where DirID indicates the directory where access consistency needs to be configured, AccessConsistencyLevel indicates the access consistency that needs to be configured for the directory, and Bool ifSonInheritance indicates the directory. Whether the subordinate objects of the directory inherit the access consistency of the directory configuration.
  • Bool ifSonInheritance When Bool ifSonInheritance is assigned a value of true, it means that the subordinate objects of the directory inherit the access consistency of the directory configuration. When the assignment of Bool ifSonInheritance is false, it means that the subordinate objects of the directory inherit the access consistency of the directory configuration. Access consistency configured for the directory is not inherited.
  • the operation instruction does not need to carry DirID, that is, does not indicate a directory.
  • the access consistency of all directories used by the user who sends the operation instruction can be set according to the operation instruction.
  • the operation instruction can also carry FileSystemId, that is, indicating the file system.
  • the access consistency of the directory of the file system indicated by the operation instruction can be set.
  • the operation instruction does not indicate a file system
  • the access consistency of the operation instruction to the directory currently using the file system of the user who sends the operation instruction can be set.
  • the operation command does not need to carry AccessConsistencyLeve, that is, the access consistency that needs to be set is not specified. In this case, it means that the directory inherits the access consistency of its superior object.
  • parameters that need to be carried by the operation instructions can be set according to application requirements, which are not specifically limited in the embodiments of this application.
  • the fifth operation Modify the access consistency of the directory.
  • this configuration operation there are two implementations of this configuration operation: the first implementation is to modify the access consistency of the directory, and the subordinate objects of the configuration directory inherit the modified access consistency of the directory; the second implementation is to In this case, the access consistency of the directory is modified, and the subordinate objects of the configuration directory do not inherit the modified access consistency of the directory.
  • the operation instructions can be implemented in different ways.
  • subordinate objects of a directory can inherit the modified access consistency of the directory by default.
  • the operation instruction may or may not carry a parameter indicating whether to inherit.
  • the operation instruction needs to carry parameters indicating whether to inherit it.
  • the operation instruction can be: Modify Dir Access Consistency Level (DirID, AccessConsistencyLevel), where DirID indicates the directory whose access consistency needs to be modified, and AccessConsistencyLevel indicates the modified access consistency of the directory.
  • the operation instruction can be: Modify Dir Access Consistency Level (DirID, AccessConsistencyLevel, Bool ifSonInheritance), where DirID indicates the directory whose access consistency needs to be modified, AccessConsistencyLevel indicates the modified access consistency of the directory, and Bool ifSonInheritance indicates the subordinate level of the directory. Whether the object inherits the modified access consistency of the directory.
  • Bool ifSonInheritance When Bool ifSonInheritance is assigned a value of true, it means that the subordinate objects of the directory inherit the modified access consistency of the directory. When Bool ifSonInheritance is assigned a value of false, it means that the subordinate objects of the directory do not inherit it. Directory modified access Ask about consistency.
  • the operation instruction does not need to carry DirID, that is, does not indicate a directory.
  • the access consistency of all directories used by the user who sends the operation instruction can be modified according to the operation instruction.
  • the operation instruction can also carry the FileSystemId, that is, indicating the file system.
  • the access consistency of the directory of the file system indicated by the operation instruction can be modified.
  • the operation instruction does not indicate a file system
  • the access consistency of the operation instruction to the directory currently using the file system of the user who sent the operation instruction can be modified.
  • the operation command does not need to carry AccessConsistencyLeve, that is, the access consistency that needs to be modified is not specified. In this case, it means that the directory inherits the access consistency of its superior object.
  • parameters that need to be carried by the operation instructions can be set according to application requirements, which are not specifically limited in the embodiments of this application.
  • the sixth operation Query the access consistency of the directory.
  • the operation instruction can be: Get Dir Access Consistency Level (DirID), where DirID indicates the directory to be queried. It should be noted that the operation instruction does not need to carry DirID, that is, does not indicate a directory. In this case, the access consistency of all directories used by the user who sends the operation instruction can be queried based on the operation instruction.
  • DirID Dir Access Consistency Level
  • the operation instruction can also carry FileSystemId, which indicates the file system.
  • FileSystemId indicates the file system.
  • the access consistency of the directory of the file system indicated by the operation instruction can be queried.
  • the operation instruction does not indicate a file system
  • the access consistency of the operation instruction to the directory currently using the file system of the user who sent the operation instruction can be queried.
  • parameters that need to be carried by the operation instructions can be set according to application requirements, which are not specifically limited in the embodiments of this application.
  • the seventh operation configure file access consistency.
  • the operation instruction can be: Set File Access Consistency Level (FileID, AccessConsistencyLevel), where FileID indicates the file for which access consistency needs to be configured, and AccessConsistencyLevel indicates the access consistency that needs to be configured for the file.
  • FileID indicates the file for which access consistency needs to be configured
  • AccessConsistencyLevel indicates the access consistency that needs to be configured for the file.
  • the operation instruction does not need to carry a FileID, that is, does not indicate a file.
  • the access consistency of all files used by the user who sends the operation instruction can be set according to the operation instruction.
  • the operation instruction can also carry DirId, which indicates the directory to which the file belongs. In this case, the access consistency of the files in the directory indicated by the operation instruction can be set.
  • the operation instruction does not indicate a directory, you can set the access consistency of the operation instruction to files in the directory currently used by the user who sends the operation instruction.
  • the operation instruction can also carry the FileSystemId, that is, indicating the file system. In this case, the access consistency of the files in the file system indicated by the operation instruction can be set.
  • the operation instruction does not indicate a file system
  • the operation command does not need to carry AccessConsistencyLeve, that is, the access consistency that needs to be set is not specified. In this case, it means that the file inherits the access consistency of its superior object.
  • the eighth operation Modify the access consistency of the file.
  • the operation instruction can be: Modify File Access Consistency Level (FileID, AccessConsistencyLevel), where FileID indicates the file whose access consistency needs to be modified, and AccessConsistencyLevel indicates the modified access consistency of the file.
  • FileID indicates the file whose access consistency needs to be modified
  • AccessConsistencyLevel indicates the modified access consistency of the file.
  • the operation instruction does not need to carry a FileID, that is, does not indicate a file.
  • the access consistency of all files used by the user who sends the operation instruction can be modified according to the operation instruction.
  • the operation instruction can also carry DirId, which indicates the directory to which the file belongs. In this case, the access consistency of the files in the directory indicated by the operation instruction can be set.
  • the operation instruction does not indicate a directory, you can set the access consistency of the operation instruction to files in the directory currently used by the user who sends the operation instruction.
  • the operation instruction can also carry a FileSystemId, which indicates the file system. In this case, the access consistency of the files in the file system indicated by the operation instruction can be modified.
  • the access consistency of the operation instruction to files currently using the file system of the user who sends the operation instruction can be modified at this time.
  • the operation command does not need to carry AccessConsistencyLeve, that is, the access consistency that needs to be modified is not specified. In this case, it means that the file inherits the access consistency of its superior object.
  • the ninth operation Query the access consistency of the file.
  • the operation instruction can be: Get File Access Consistency Level (FileID), where FileID indicates the file to be queried.
  • the operation instruction does not need to carry a FileID, that is, does not indicate a file.
  • the operation instruction can also carry DirId, which indicates the directory to which the file belongs.
  • DirId which indicates the directory to which the file belongs.
  • the access consistency of the files in the directory indicated by the operation instruction can be set.
  • the operation instruction can also carry FileSystemId, which indicates the file system. In this case, the access consistency of the files in the file system indicated by the operation instruction can be queried.
  • the access consistency of the operation instruction to files currently using the file system of the user who sent the operation instruction can be queried.
  • the implementation of file system access consistency can include multiple implementations.
  • the embodiments of this application are as follows: Take the implementation as an example to explain the implementation of access consistency:
  • access consistency indicates that after a write operation is performed on the target object, a read operation on the target object can read the data after the write operation.
  • the access consistency of this implementation can be called read after write (Read after write), which indicates that for any file f, client a has modified it, then at the time after the modification, if client b If file f performs a read operation, the modified new value should be read.
  • access consistency indicates: after a write operation is performed on the target object and the target object is refreshed, a read operation on the target object can read the data after the write operation.
  • refresh can be implemented through synchronization operations (such as sync synchronization).
  • the access consistency of this implementation can be called Read after sync, which indicates that for any file f, client a has modified it, then at the post-modification time, if client b modifies the file When f performs a read operation, the file needs to be synchronized before the modified new value can be read.
  • access consistency indicates: after a write operation is performed on the target object and the target object is restarted, a read operation on the target object can read the data after the write operation.
  • restarting can be accomplished by closing and reopening the file.
  • the access consistency of this implementation can be called read after close, which indicates that for any file f, client a has modified it, then at the post-modification time, if client b modifies the file f performs a read operation, the file needs to be closed and reopened before the new modified value can be read.
  • Step 402 Based on the operation instruction, perform the operation indicated by the operation instruction on the target object.
  • the computer device After receiving the operation instruction, the computer device can perform the operation indicated by the operation instruction on the target object based on the operation instruction, thereby achieving consistent access to the target object.
  • the function of operating the access consistency of the target object of the file system can be implemented in a variety of ways.
  • it can be implemented by calling an application programming interface (API).
  • API application programming interface
  • the file system can be configured with an application program interface for implementing all operations it supports. After the computer device receives the operation instruction, it can call the application program interface for implementing the operation indicated by the operation instruction to implement the operation instruction through it. Instructed action.
  • Step 403 Receive an access instruction, which indicates access to the target object.
  • the user can trigger an access instruction through some operations, so that the computer device can feedback to the user the content it requests to access based on the access instruction.
  • the user can trigger the client to send the access instruction to the cloud platform by performing some operations, so that the cloud platform can This access command provides feedback to the user about the contents of the file that he or she is requesting access to.
  • Step 404 Based on the access consistency of the target object, respond to the access instruction according to the state after performing the operation indicated by the operation instruction on the target object.
  • the computer device After receiving the access instruction, the computer device can obtain the current status of the target object, and respond to the access request based on the status and the access consistency of the target object. For example, when the access instruction is a read instruction, the description will continue to take three implementation situations of access consistency in step 401 as an example.
  • the client For the implementation of Read after write, no matter what the current status of the file f requested by the access command is, through the computer device's response to the access command, the client can read the value of the last modification to file f before the read command.
  • Read after sync if the current status of file f is that sync synchronization has not been performed after modification, through the computer device's response to the access command, the client cannot read the value of the last modification to file f before the read command.
  • the client can read the value of the last modification to file f before the read instruction through the computer device's response to the access command.
  • Read after close if the current status of file f is not closed after modification, through the computer device's response to the access command, the client cannot read the value of the last modification to file f before the read command. If The current status of file f is that it has been closed after modification. Only through the computer device's response to the access command can the client read the value of the last modification to file f before the read command.
  • the user when creating a file system, the user can trigger an operation instruction through an operation to instruct the access consistency of the file system to be set to level 1, and then the computer device can set the access consistency of the file system to level 1 based on the operation instruction. , such as setting the access consistency of the root directory of the file system to level1.
  • the user creates directory 1, file 1, directory 2 and file 2 , neither of them indicates their access consistency, then directory 1 and file 1 inherit the access consistency level 1 of their upper-level object (the root directory in Figure 5), and directory 2 and file 2 inherit the access consistency level 1 of their upper-level object (directory 1 in Figure 5). ) access consistency level1.
  • the user when creating a file system, the user can trigger an operation instruction through an operation to instruct the access consistency of the file system to be set to level 1, and then the computer device can set the access consistency of the file system to level 1 based on the operation instruction. , such as setting the access consistency of the root directory of the file system to level1.
  • the user did not indicate access consistency when creating directory 1, file 1, and file 2.
  • directory 1 and file 1 inherit the access consistency of their superior objects (the root directory in Figure 6).
  • Level 1, file 2 inherits the access consistency level 1 of its superior object (directory 1 in Figure 6).
  • file 3 inherits the access consistency level 3 of its superior object (directory 1 in Figure 6) (i.e. Modified access consistency).
  • directory 1 in Figure 6 i.e. Modified access consistency
  • file 1 and file 2 need to inherit the access consistency of their upper-level objects
  • the access consistency of the corresponding upper-level objects needs to be queried.
  • the numbers in parentheses after the object in Figure 6 represent the access consistency of the object
  • the numbers at the end of the arrow represent the access consistency before the change
  • the numbers at the head of the arrow represent the access consistency after the change.
  • the user when creating a file system, the user can trigger an operation instruction through an operation to instruct the access consistency of the file system to be set to level 1, and then the computer device can set the access consistency of the file system to level 1 based on the operation instruction. , such as setting the access consistency of the root directory of the file system to level1.
  • the user did not indicate access consistency when creating directory 1, file 1, and directory 2.
  • directory 1 and file 1 inherit the access consistency of their superior objects (the root directory in Figure 7).
  • Level 1, directory 2 inherits the access consistency level 1 of its superior object (directory 1 in Figure 7).
  • the computer device when the file system is in a state that can be used, the computer device can receive the operation instruction sent by the first client, and based on the operation instruction, perform the operation on the target The object performs the operation indicated by the operation instruction.
  • the operation instruction indicates operating on the access consistency of the target object of the file system. Since when the file system is in a usable state, the computer device can operate on the access consistency of the target object of the file system based on the operation instructions, so that the access consistency of the file system can be changed after the design is completed. , which makes it easy to adjust the access consistency of file system objects according to different application requirements, so that the file system can meet the application requirements of different application scenarios, and effectively improves the usability of the file system.
  • the management device 80 of the file system includes:
  • the interaction module 801 is configured to receive an operation instruction when the file system is in a usable state, and the operation instruction instructs to operate on the access consistency of the target object of the file system.
  • the processing module 802 is configured to perform the operation indicated by the operation instruction on the target object based on the operation instruction.
  • the target object includes one or more of the following: root directory, directory, and file of the file system.
  • different target objects in the file system can be configured to have different access consistency.
  • the operation includes one or more of the following: configuring the access consistency of the target object; modifying the access consistency of the target object; and querying the access consistency of the target object.
  • configuring the access consistency of the target object includes one or more of the following: configuring the access consistency of the target object, and configuring the target object's subordinate objects to inherit the target object configuration access consistency; configure the access of the target object Ask for consistency, and the subordinate objects configured for the target object do not inherit the access consistency configured for the target object.
  • modifying the access consistency of the target object includes one or more of the following: modifying the access consistency of the target object, and configuring the subordinate objects of the target object to inherit the modified access consistency of the target object. Access consistency; and, modify the access consistency of the target object, and configure the subordinate objects of the target object not to inherit the modified access consistency of the target object.
  • access consistency includes one or more of the following:
  • the read operation on the target object can read the data after the write operation
  • the read operation on the target object can read the data after the write operation
  • the read operation on the target object can read the data after the write operation.
  • the interaction module 801 is also used to receive an access instruction, which indicates access to the target object; the processing module 802 is also used to perform the operation indicated by the operation instruction on the target object based on the access consistency of the target object. status to respond to access instructions.
  • the interaction module can receive the operation instruction sent by the first client, and the processing module can, based on the operation instruction, Perform the operation indicated by the operation instruction on the target object.
  • the operation instruction indicates operating on the access consistency of the target object of the file system.
  • the management device of the file system can operate on the access consistency of the target object of the file system based on the operation instructions, so that after the design of the file system is completed, its access consistency It can also be changed, so that the access consistency of file system objects can be adjusted according to different application requirements, so that the file system can meet the application requirements of different application scenarios, effectively improving the availability of the file system.
  • FIG. 9 is a schematic structural diagram of a computer device provided by an embodiment of the present application.
  • the computer device 900 includes a processor 901, a memory 902, a communication interface 903 and a bus 904. Among them, the processor 901, the memory 902, and the communication interface 903 implement communication connections between each other through the bus 904.
  • Processor 901 may include a general-purpose processor and/or a special-purpose hardware chip.
  • General-purpose processors can include: central processing unit (CPU), microprocessor or graphics processing unit (GPU).
  • the CPU is, for example, a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a dedicated hardware chip is a high-performance processing hardware module.
  • Specialized hardware chips include at least one of digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or network processors (network processors, NPs).
  • ASICs application-specific integrated circuits
  • FPGAs field-programmable gate arrays
  • NPs network processors
  • the processor 901 may also be an integrated circuit chip with signal processing capabilities. During the implementation process, part or all of the functions of the file system management method of the present application can be completed by instructions in the form of hardware integrated logic circuits or software in the processor 901 .
  • the memory 902 is used to store computer programs, which include an operating system 902a and executable codes (ie, program instructions) 902b.
  • the memory 902 is, for example, a read-only memory or other type of static storage device that can store static information and instructions, or a random access memory or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable memory device.
  • the memory 902 is used to store outbound port queues, etc.
  • the memory 902 exists independently, for example, and is connected to the processor 901 through a bus 904 . Or the memory 902 and the processor 901 are integrated together.
  • the memory 902 may store executable code.
  • the processor 901 is configured to perform part or all of the functions of the file system management method provided by the embodiment of the present application.
  • the memory 902 may also include operating systems and other software modules and data required for running processes.
  • the communication interface 903 uses a transceiver module such as but not limited to a transceiver to implement communication with other devices or communication networks.
  • the communication interface 903 may be any one or any combination of the following devices: a network interface (such as an Ethernet interface), a wireless network card, and other devices with network access functions.
  • Bus 904 is any type of communication bus used to interconnect internal components of a computer device (eg, memory 902, processor 901, communication interface 903).
  • a computer device eg, memory 902, processor 901, communication interface 903
  • system bus e.g., system bus.
  • the embodiment of the present application takes the above-mentioned devices inside the computer device as being interconnected through the bus 904 as an example.
  • the above-mentioned devices inside the computer device 900 may also use other connection methods besides the bus 904 to communicate with each other.
  • the above-mentioned devices inside the computer device 900 are interconnected through internal logical interfaces.
  • the above-mentioned plurality of devices can be respectively arranged on independent chips, or at least part or all of them can be arranged on the same chip. Whether each device is independently installed on different chips or integrated on one or more chips often depends on the needs of product design.
  • the embodiments of this application do not limit the specific implementation forms of the above devices.
  • the descriptions of the processes corresponding to each of the above drawings have different emphases. For parts that are not detailed in a certain process, you can refer to the relevant descriptions of other processes.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product that provides a program development platform includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer device, the functions of the file system management method provided by the embodiments of the present application are fully or partially implemented.
  • computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
  • computer instructions may be transmitted over a wired connection from a website, computer, server or data center. (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center.
  • the computer-readable storage medium stores computer program instructions that provide a program development platform.
  • An embodiment of the present application also provides a computer cluster.
  • the computer cluster includes multiple computer devices, the multiple computer devices include multiple processors and multiple memories, program instructions are stored in the multiple memories, and the multiple processors run the program instructions, so that the computer cluster is used to implement the implementation of this application.
  • the example provides the function of file system management method.
  • For the implementation method of each computer device in the computer cluster please refer to the implementation method of the aforementioned computer equipment accordingly, which will not be described again here.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium is a non-volatile computer-readable storage medium.
  • the computer-readable storage medium includes program instructions. When the program instructions are run on a computer device At this time, the computer device is caused to implement the file system management method provided by the embodiment of the present application.
  • An embodiment of the present application also provides a computer program product containing instructions.
  • the computer program product When the computer program product is run on a computer, the computer implements the file system management method provided by the embodiment of the present application.
  • the information including but not limited to user equipment information, user personal information, etc.
  • data including but not limited to data used for analysis, stored data, displayed data, etc.
  • signals involved in this application All are authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
  • the operation instructions and access instructions involved in this application were obtained with full authorization.
  • the terms “first”, “second” and “third” are only used for description purposes and cannot be understood as indicating or implying relative importance.
  • the term “at least one” refers to one or more, and the term “plurality” refers to two or more, unless expressly limited otherwise.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请公开了一种文件系统的管理方法及装置，属于文件系统技术领域。该方法包括：在文件系统处于能够被使用的状态时，接收操作指令，操作指令指示针对文件系统的目标对象的访问一致性进行操作；基于操作指令，对目标对象执行操作指令指示的操作。本申请使得文件系统在设计完成后，其访问一致性还能够被改变，这样就能够便于根据不同的应用需求调整文件系统的对象的访问一致性。

Description

文件系统的管理方法及装置
本申请要求于2022年08月18日提交的申请号为202210995892.8、发明名称为“文件处理方法及装置”的中国专利申请的优先权，及于2022年11月10日提交的申请号为202211406915.3、发明名称为“文件系统的管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及文件系统技术领域，特别涉及一种文件系统的管理方法及装置。
背景技术
文件系统(如分布式文件系统(distributed file system，DFS))是集高可靠性、高扩展性、高性能于一体的主流存储系统，目前广泛应用于媒资、高算、基因等场景。并且，不同的应用场景，对文件系统的访问一致性(consistency)提出不同的应用需求。其中，访问一致性要求：在不同客户端对文件系统的同一内容的访问间隙中，该内容没有被修改的前提下，不同客户端访问该内容得到的数据需要完全相同。
目前，在完成文件系统的设计后，文件系统的访问一致性级别就确定了，其难以应用于具有不同应用需求的不同应用场景，导致文件系统的可用性较差。
发明内容
本申请提供了一种文件系统的管理方法及装置。本申请使得文件系统在设计完成后，其访问一致性还能够被改变，这样就能够便于根据不同的应用需求调整文件系统的对象的访问一致性。本申请提供的技术方案如下：
第一方面，本申请提供了一种文件系统的管理方法。该方法包括：在文件系统处于能够被使用的状态时，接收操作指令，操作指令指示针对文件系统的目标对象的访问一致性进行操作；基于操作指令，对目标对象执行操作指令指示的操作。
在本申请提供的文件系统的管理方法中，在文件系统处于能够被使用的状态时，计算机设备能够接收第一客户端发送的操作指令，并基于操作指令，对目标对象执行操作指令指示的操作。其中，该操作指令指示针对文件系统的目标对象的访问一致性进行操作。由于在文件系统在处于能够被使用的状态的情况下，计算机设备能够基于操作指令针对文件系统的目标对象的访问一致性进行操作，使得文件系统在设计完成后，其访问一致性还能够被改变，这样就能够便于根据不同的应用需求调整文件系统的对象的访问一致性，使得文件系统能够满足不同应用场景的应用需求，有效地提高了文件系统的可用性。
其中，目标对象包括以下一种或多种：文件系统的根目录、目录和文件。
由于计算机设备能够根据操作指令对目标对象执行对应的访问一致性操作，使得文件系统中不同目标对象能够配置为具有不同的访问一致性。这样一来，同一文件系统就能够并行支持多种访问一致性，进一步地提高了文件系统的灵活性和文件系统的可用性。
在一种实现方式中，操作包括以下一种或多种：配置目标对象的访问一致性；修改目标对象的访问一致性；以及，查询目标对象的访问一致性。
可选的，当目标对象为文件系统和/或目录时，由于该目标对象有下级对象，在对目标对象的访问一致性进行配置和时，还可以配置该目标对象的下级对象是否继承为该目标对象配置的访问一致性。也即是，目标对象为文件系统和/或目录时，配置目标对象的访问一致性包括以下一种或多种：配置目标对象的访问一致性，且配置目标对象的下级对象继承为目标对象配置的访问一致性；配置目标对象的访问一致性，且配置目标对象的下级对象不继承为目标对象配置的访问一致性。
类似的，目标对象为文件系统和/或目录时，修改目标对象的访问一致性包括以下一种或多种：修改目标对象的访问一致性，且配置目标对象的下级对象继承目标对象修改后的访问一致性；以及，修改目标对象的访问一致性，且配置目标对象的下级对象不继承目标对象修改后的访问一致性。
通过配置目标对象的下级对象是否继承目标对象的访问一致性，在更细的粒度上丰富了文件系统中对象的访问一致性的可配置程度，能够更好地满足用户对文件系统的对象的访问一致性诉求。
对应于不同的应用需求，文件系统的访问一致性的实现情况可以包括多种。在一种实现方式中，访问一致性包括以下一种或多种：在对目标对象执行写操作后，对目标对象的读操作能够读取到执行写操作后的数据；在对目标对象执行写操作，且对目标对象进行刷新后，对目标对象的读操作能够读取到执行写操作后的数据；在对目标对象执行写操作，且重启目标对象后，对目标对象的读操作能够读取到执行写操作后的数据。
可选的，在基于操作指令，对目标对象执行操作指令指示的操作之后，该方法还包括：接收访问指令，访问指令指示对目标对象进行访问；基于目标对象的访问一致性，按照对目标对象执行操作指令指示的操作后的状态，对访问指令进行响应。
第二方面，本申请提供了一种文件系统的管理装置。该文件系统的管理装置包括：交互模块，用于在文件系统处于能够被使用的状态时，接收操作指令，操作指令指示针对文件系统的目标对象的访问一致性进行操作；处理模块，用于基于操作指令，对目标对象执行操作指令指示的操作。
可选的，目标对象包括以下一种或多种：文件系统的根目录、目录和文件。
可选的，文件系统中不同目标对象能够配置为具有不同的访问一致性。
可选的，操作包括以下一种或多种：配置目标对象的访问一致性；修改目标对象的访问一致性；以及，查询目标对象的访问一致性。
可选的，目标对象为文件系统和/或目录时，配置目标对象的访问一致性包括以下一种或多种：配置目标对象的访问一致性，且配置目标对象的下级对象继承为目标对象配置的访问一致性；配置目标对象的访问一致性，且配置目标对象的下级对象不继承为目标对象配置的访问一致性。
类似的，目标对象为文件系统和/或目录时，修改目标对象的访问一致性包括以下一种或多种：修改目标对象的访问一致性，且配置目标对象的下级对象继承目标对象修改后的访问一致性；以及，修改目标对象的访问一致性，且配置目标对象的下级对象不继承目标对象修改后的访问一致性。
可选的，访问一致性包括以下一种或多种：在对目标对象执行写操作后，对目标对象的读操作能够读取到执行写操作后的数据；在对目标对象执行写操作，且对目标对象进行刷新后，对目标对象的读操作能够读取到执行写操作后的数据；在对目标对象执行写操作，且重启目标对象后，对目标对象的读操作能够读取到执行写操作后的数据。
可选的，交互模块，还用于接收访问指令，访问指令指示对目标对象进行访问；处理模块，还用于基于目标对象的访问一致性，按照对目标对象执行操作指令指示的操作后的状态，对访问指令进行响应。
第三方面，本申请提供了一种计算机设备，包括存储器和处理器，存储器存储有程序指令，处理器运行程序指令以执行本申请第一方面以及其任一种可能的实现方式中提供的方法。
第四方面，本申请提供了一种计算机集群，包括多个计算机设备，多个计算机设备包括多个处理器和多个存储器，多个存储器中存储有程序指令，多个处理器运行程序指令，使得计算机集群执行本申请第一方面以及其任一种可能的实现方式中提供的方法。
第五方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质为非易失性计算机可读存储介质，该计算机可读存储介质包括程序指令，当程序指令在计算机设备上运行时，使得计算机设备执行本申请第一方面以及其任一种可能的实现方式中提供的方法。
第六方面，本申请提供了一种包含指令的计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机执行本申请第一方面以及其任一种可能的实现方式中提供的方法。
附图说明
图1是本申请实施例提供的一种文件系统的示意图；
图2是本申请实施例提供的一种文件系统的管理方法涉及的实施环境的示意图；
图3是本申请实施例提供的另一种文件系统的管理方法涉及的实施环境的示意图；
图4是本申请实施例提供的一种文件系统的管理方法的流程图；
图5是本申请实施例提供的一种访问一致性的操作示意图；
图6是本申请实施例提供的另一种访问一致性的操作示意图；
图7是本申请实施例提供的又一种访问一致性的操作示意图；
图8是本申请实施例提供的一种文件系统的管理装置的示意图；
图9是本申请实施例提供的一种计算机设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
为便于理解，下面先对本申请实施例中涉及的关联技术和背景进行介绍。
文件系统是操作系统用于明确存储设备(如磁盘、固态硬盘等)或分区上的文件的方法和数据结构，用于管理和存储文件的文件信息。从系统角度来看，文件系统是对文件存储设备的空间进行组织和分配，负责文件存储并对存入的文件进行保护和检索的系统。例如，文件系统负责为用户建立文件、存入文件、读出文件的数据、修改文件的数据、转存文件、控制文件的存取、以及当用户不再使用时撤销文件等。
文件系统包括三部分：文件系统的接口、对对象操纵和管理的软件集合、及文件系统的对象。文件系统的对象包括：根目录(ROOT)、目录(directory)和文件(file)。文件系统及其对象之间的关系可以采用树状结构表示，如图1所示，文件系统包括根目录、目录和文件。根目录的下级对象可以包括目录1和文件1等，目录1的下级对象包括目录2和文件2等，以此类推。
文件系统(如分布式文件系统)是集高可靠性、高扩展性、高性能于一体的主流存储系统，目前广泛应用于媒资、高算、基因等场景。并且，不同的应用场景，对文件系统的访问一致性提出不同的应用需求。其中，访问一致性要求：在不同客户端对文件系统的同一内容的访问间隙中，该内容没有被修改的前提下，不同客户端访问该内容得到的数据需要完全相同。
目前，在完成文件系统的设计后，文件系统的访问一致性级别就确定了，文件系统只能按照其已经确定的访问一致性工作。并且，文件系统仅支持一种访问一致性，导致文件系统中的所有目录和文件都只能按照该访问一致性工作。因此，目前的文件系统难以应用于具有不同应用需求的不同应用场景，导致文件系统的可用性较差。
本申请实施例提供了一种文件系统的管理方法及装置。在该文件系统的管理方法中，在文件系统处于能够被使用的状态时，计算机设备能够接收第一客户端发送的操作指令，并基于操作指令，对目标对象执行操作指令指示的操作。其中，该操作指令指示针对文件系统的目标对象的访问一致性进行操作。
由于在文件系统在处于能够被使用的状态的情况下，计算机设备能够基于操作指令针对文件系统的目标对象的访问一致性进行操作，使得文件系统在设计完成后，其访问一致性还能够被改变，这样就能够便于根据不同的应用需求调整文件系统的对象的访问一致性，使得文件系统能够满足不同应用场景的应用需求，有效地提高了文件系统的可用性。
图2是本申请实施例提供的一种文件系统的管理方法涉及的实施环境的结构示意图。如图2所示，该实施环境包括：计算机设备10。该计算机设备10中可以运行有文件系统，用户可以使用文件系统对其文件进行管理。并且，用户在需要针对其文件系统的对象的访问一致性进行操作时，可以向该计算机设备10发送操作指令，以指示计算机设备10针对文件系统的目标对象的访问一致性进行操作。计算机设备10接收到操作指令后，可以基于该操作指令，对目标对象执行操作指令指示的操作，以便于在接收到指示对该目标对象进行访问的访问指令后，计算机设备10能够按照对目标对象执行操作指令指示的操作后的状态，对访问指令进行响应。
在该实施环境中，本申请实施例提供的文件系统的管理方法，可以通过计算机设备10运行可执行程序实现。例如，该文件系统的管理方法的可执行程序可以以应用程序安装包的形式呈现，计算机设备10中安装该应用程序安装包后，就能够通过运行该可执行程序实现该文件系统的管理方法。此时，计算机设备10可以为终端。该终端可以为计算机、个人电脑、便携式移动终端、多媒体播放器、电子书阅读器或可穿戴式设备等。
在另一种实施环境中，如图3所示，该实施环境可以包括计算机设备10和客户端20。客户端20能够 与计算机设备10建立通信连接。例如，客户端20与计算机设备10之间可以通过网络建立通信连接。可选的，该网络可以为局域网，也可以为互联网，还可以为其它网络，本申请实施例不作限定。
在该图3的实施环境中，用户可以通过客户端20与计算机设备10交互。例如，用户可以通过客户端20向计算机设备10发送操作指令和访问指令等指令。计算机设备10用于运行有文件系统，通过文件系统对用户的文件进行管理，并在接收到客户端20发送的指令后，根据指令进行响应。例如，在用户通过客户端20向计算机设备10发送操作指令后，计算机设备10可以按照该操作指令的指示，对文件系统的目标对象的访问一致性进行操作。又例如，在用户通过客户端20向计算机设备10发送对目标对象访问指令后，计算机设备10可以基于访问指令进行响应。
在一种实现方式中，客户端20可以为计算机、个人电脑、膝上型计算机、移动电话、智能手机、平板电脑、云主机、便携式移动终端、多媒体播放器、电子书阅读器、可穿戴式设备、智能家电、人工智能设备、智能可穿戴设备、智能车载设备或物联网设备等。计算机设备10可以为服务器。且服务器可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是一个云计算服务中心。其中，云计算服务中心中部署有云服务提供商拥有的大量基础资源。例如云计算服务中心中部署有计算资源、存储资源和网络资源等。云计算服务中心可以利用该大量基础资源，运行文件系统，并实现本申请实施例提供的文件系统的管理方法。
当服务器通过云计算服务中心实现时。用户可以通过客户端20访问云平台，并通过云平台使用文件系统。此时，服务器为用户提供文件系统及文件系统的管理方法的功能，可以由云服务提供商在云平台抽象成一种文件系统云服务。用户在云平台购买文件系统云服务后，云平台能够利用云计算中心中的资源向用户提供文件系统，并使用本申请实施例提供的文件系统的管理方法对文件系统进行管理。可选地，云平台可以是中心云的云平台、边缘云的云平台或包括中心云和边缘云的云平台，本申请实施例对其不做具体限定。
需要说明的是，在图3所示的实施环境中，计算机设备10也可以通过除云平台外的其他资源平台实现，本申请实施例对其不做具体限定。此时，服务器可以通过其他资源平台中的资源实现，并向用户提供文件系统的相关服务。
应当理解的是，以上内容是对本申请实施例提供的文件系统的管理方法的应用场景的示例性说明，并不构成对于该文件系统的管理方法的应用场景的限定，本领域普通技术人员可知，随着业务需求的改变，其应用场景可以根据应用需求进行调整，本申请实施例对其不做一一列举。
下面对本申请实施例提供的文件系统的管理方法进行说明。如图4所示，该文件系统的管理方法包括以下步骤：
步骤401、在文件系统处于能够被使用的状态时，接收操作指令，操作指令指示针对文件系统的目标对象的访问一致性进行操作。
在使用文件系统的用户需要对文件系统的目标对象的访问一致性进行操作时，用户可以通过一些操作触发操作指令，以便于计算机设备能够基于该操作指令，对文件系统的目标对象的访问一致性进行操作。例如，当用户在使用云平台提供的文件系统云服务时，用户在基于其业务需求确定需要针对文件系统的目标对象的访问一致性进行操作时，用户可以通过执行一些操作触发客户端向云平台发送该操作指令，以便于云平台基于该操作指令对文件系统的目标对象的访问一致性进行操作。其中，文件系统处于能够被使用的状态，是指已完成了对文件系统的设计。
可选的，文件系统的目标对象包括以下一种或多种：文件系统的根目录、目录和文件等粒度的组成部分。其中，对文件的根目录进行操作就是对整个文件系统进行操作。并且，文件系统的文件可以是根目录的下级文件，也可以是目录的下级文件。需要说明的是，当文件系统还有其他粒度的组成部分时，该目标对象还可以为其他粒度。并且，当目标对象为文件系统的根目录、目录和文件等粒度的组成部分时，通过针对对应粒度的组成部分的访问一致性进行操作，使得能够针对不同用户对该粒度的组成部分的一致性诉求，提供不同等级的访问一致性，能够向用户提供更灵活的文件系统。
在本申请实施例中，能够对目标对象执行的操作包括以下一种或多种：配置目标对象的访问一致性，修改目标对象的访问一致性，以及，查询目标对象的访问一致性。该配置操作用于在创建目标对象时，对目标对象的访问一致性进行配置。该修改操作用于在目标对象已经配置有访问一致性的情况下，对目标对 象的访问一致性进行修改。
并且，当目标对象为文件系统和/或目录时，由于该目标对象有下级对象，在对目标对象的访问一致性进行配置和时，还可以配置该目标对象的下级对象是否继承为该目标对象配置的访问一致性。也即是，配置目标对象的访问一致性可以包括：配置目标对象的访问一致性，且配置目标对象的下级对象继承为目标对象配置的访问一致性；配置目标对象的访问一致性，且配置目标对象的下级对象不继承为目标对象配置的访问一致性。和/或，修改目标对象的访问一致性可以包括：修改目标对象的访问一致性，且配置目标对象的下级对象继承目标对象修改后的访问一致性；修改目标对象的访问一致性，且配置目标对象的下级对象不继承目标对象修改后的访问一致性。通过配置目标对象的下级对象是否继承目标对象的访问一致性，在更细的粒度上丰富了文件系统中对象的访问一致性的可配置程度，能够更好地满足用户对文件系统的对象的访问一致性诉求。
另外，在本申请实施例中，由于目标对象包括以下一种或多种：文件系统的根目录、目录和文件，且计算机设备能够根据操作指令对目标对象执行对应的访问一致性操作，使得文件系统中不同目标对象能够配置为具有不同的访问一致性。这样一来，同一文件系统就能够并行支持多种访问一致性，进一步地提高了文件系统的灵活性和文件系统的可用性。
下面根据本申请实施例提供的目标对象的实现方式，及能够对目标对象执行的操作的种类，对计算机设备基于操作指令能够对文件系统执行的操作进行举例说明：
第一种操作：配置文件系统的访问一致性。并且，根据操作指令的不同，该配置操作还有两种实现情况：第一种实现情况，配置文件系统的访问一致性，且配置文件系统的下级对象继承为文件系统配置的访问一致性；第二种实现情况，配置文件系统的访问一致性，且配置文件系统的下级对象不继承为文件系统配置的访问一致性。
对应于该配置操作的不同实现情况，操作指令可以有不同的实现方式。例如，文件系统的下级对象可以默认继承为文件系统配置的访问一致性。则配置文件系统的下级对象需要继承为文件系统配置的访问一致性时，操作指令可以携带或者不携带用于指示是否继承的参数。配置文件系统的下级对象不继承为文件系统配置的访问一致性时，操作指令需要携带用于指示是否继承的参数。
作为一种示例，其操作指令可以为：Set File System Access Consistency Level(FileSystemId，AccessConsistencyLevel)，其中，FileSystemId指示需要配置访问一致性的文件系统，AccessConsistencyLevel指示需要为该文件系统配置的访问一致性。或者，其操作指令可以为：Set File System Access Consistency Level(FileSystemId，AccessConsistencyLevel，Bool ifSonInheritance)，其中，FileSystemId指示需要配置访问一致性的文件系统，AccessConsistencyLevel指示需要为该文件系统配置的访问一致性，Bool ifSonInheritance指示文件系统的下级对象是否继承为文件系统配置的访问一致性，当Bool ifSonInheritance的赋值为true时，表示文件系统的下级对象继承为文件系统配置的访问一致性，当Bool ifSonInheritance的赋值为false时，表示文件系统的下级对象不继承为文件系统配置的访问一致性。
需要说明的是，操作指令也可以不携带FileSystemId，即不指示文件系统，此时可以根据操作指令对发送操作指令的用户使用的所有文件系统的访问一致性进行设置。在对文件系统进行管理时，可以根据应用需求设置操作指令需要携带的参数，本申请实施例对其不做具体限定。
第二种操作：修改文件系统的访问一致性。并且，根据操作指令的不同，该配置操作还有两种实现情况：第一种实现情况，修改文件系统的访问一致性，且配置文件系统的下级对象继承文件系统修改后的访问一致性；第二种实现情况，修改文件系统的访问一致性，且配置文件系统的下级对象不继承文件系统修改后的访问一致性。
对应于该配置操作的不同实现情况，操作指令可以有不同的实现方式。例如，文件系统的下级对象可以默认继承文件系统修改后的访问一致性。则配置文件系统的下级对象需要继承文件系统修改后的访问一致性时，操作指令可以携带或者不携带用于指示是否继承的参数。配置文件系统的下级对象不继承文件系统修改后的访问一致性时，操作指令需要携带用于指示是否继承的参数。
作为一种示例，其操作指令可以为：Modify File System Access Consistency Level(FileSystemId，AccessConsistencyLevel)，其中，FileSystemId指示需要修改访问一致性的文件系统，AccessConsistencyLevel指示该文件系统修改后的访问一致性。或者，其操作指令可以为：Modify File System Access Consistency Level(FileSystemId，AccessConsistencyLevel，Bool ifSonInheritance)，其中，FileSystemId指示需要修改 访问一致性的文件系统，AccessConsistencyLevel指示文件系统修改后的访问一致性，Bool ifSonInheritance指示文件系统的下级对象是否继承文件系统修改后的访问一致性，当Bool ifSonInheritance的赋值为true时，表示文件系统的下级对象继承文件系统修改后的访问一致性，当Bool ifSonInheritance的赋值为false时，表示文件系统的下级对象不继承文件系统修改后的访问一致性。
需要说明的是，操作指令也可以不携带FileSystemId，即不指示文件系统，此时可以根据操作指令对发送操作指令的用户使用的所有文件系统的访问一致性进行修改。在对文件系统进行管理时，可以根据应用需求设置操作指令需要携带的参数，本申请实施例对其不做具体限定。
第三种操作：查询文件系统的访问一致性。作为一种示例，其操作指令可以为：Get File System Access Consistency Level(FileSystemId)，其中，FileSystemId指示需要查询的文件系统。
需要说明的是，操作指令也可以不携带FileSystemId，即不指示文件系统，此时可以根据操作指令对发送操作指令的用户使用的所有文件系统的访问一致性进行查询。在对文件系统进行管理时，可以根据应用需求设置操作指令需要携带的参数，本申请实施例对其不做具体限定。
第四种操作：配置目录的访问一致性。并且，根据操作指令的不同，该配置操作还有两种实现情况：第一种实现情况，配置目录的访问一致性，且配置目录的下级对象继承为目录配置的访问一致性；第二种实现情况，配置目录的访问一致性，且配置目录的下级对象不继承为目录配置的访问一致性。
对应于该配置操作的不同实现情况，操作指令可以有不同的实现方式。例如，目录的下级对象可以默认继承为目录配置的访问一致性。则配置目录的下级对象需要继承为目录配置的访问一致性时，操作指令可以携带或者不携带用于指示是否继承的参数。配置目录的下级对象不继承为目录配置的访问一致性时，操作指令需要携带用于指示是否继承的参数。
作为一种示例，其操作指令可以为：Set Dir Access Consistency Level(DirID，AccessConsistencyLevel)，其中，DirID指示需要配置访问一致性的目录，AccessConsistencyLevel指示需要为该目录配置的访问一致性。或者，其操作指令可以为：Set Dir Access Consistency Level(DirID，AccessConsistencyLevel，Bool ifSonInheritance)，其中，DirID指示需要配置访问一致性的目录，AccessConsistencyLevel指示需要为该目录配置的访问一致性，Bool ifSonInheritance指示目录的下级对象是否继承为目录配置的访问一致性，当Bool ifSonInheritance的赋值为true时，表示目录的下级对象继承为目录配置的访问一致性，当Bool ifSonInheritance的赋值为false时，表示目录的下级对象不继承为目录配置的访问一致性。
需要说明的是，操作指令也可以不携带DirID，即不指示目录，此时可以根据操作指令对发送操作指令的用户使用的所有目录的访问一致性进行设置。并且，操作指令也可以携带FileSystemId，即指示文件系统，此时可以对操作指令指示的文件系统的目录的访问一致性进行设置。当操作指令不指示文件系统时，此时可以对操作指令对发送操作指令的用户当前使用文件系统的目录的访问一致性进行设置。另外，操作指令也可以不携带AccessConsistencyLeve，即不指定需要设置的访问一致性，此时表示目录继承其上级对象的访问一致性。在对文件系统进行管理时，可以根据应用需求设置操作指令需要携带的参数，本申请实施例对其不做具体限定。
第五种操作：修改目录的访问一致性。并且，根据操作指令的不同，该配置操作还有两种实现情况：第一种实现情况，修改目录的访问一致性，且配置目录的下级对象继承目录修改后的访问一致性；第二种实现情况，修改目录的访问一致性，且配置目录的下级对象不继承目录修改后的访问一致性。
对应于该配置操作的不同实现情况，操作指令可以有不同的实现方式。例如，目录的下级对象可以默认继承目录修改后的访问一致性。则配置目录的下级对象需要继承目录修改后的访问一致性时，操作指令可以携带或者不携带用于指示是否继承的参数。配置目录的下级对象不继承目录修改后的访问一致性时，操作指令需要携带用于指示是否继承的参数。
作为一种示例，其操作指令可以为：Modify Dir Access Consistency Level(DirID，AccessConsistencyLevel)，其中，DirID指示需要修改访问一致性的目录，AccessConsistencyLevel指示该目录修改后的访问一致性。或者，其操作指令可以为：Modify Dir Access Consistency Level(DirID，AccessConsistencyLevel，Bool ifSonInheritance)，其中，DirID指示需要修改访问一致性的目录，AccessConsistencyLevel指示目录修改后的访问一致性，Bool ifSonInheritance指示目录的下级对象是否继承目录修改后的访问一致性，当Bool ifSonInheritance的赋值为true时，表示目录的下级对象继承目录修改后的访问一致性，当Bool ifSonInheritance的赋值为false时，表示目录的下级对象不继承目录修改后的访 问一致性。
需要说明的是，操作指令也可以不携带DirID，即不指示目录，此时可以根据操作指令对发送操作指令的用户使用的所有目录的访问一致性进行修改。并且，操作指令也可以携带FileSystemId，即指示文件系统，此时可以对操作指令指示的文件系统的目录的访问一致性进行修改。当操作指令不指示文件系统时，此时可以对操作指令对发送操作指令的用户当前使用文件系统的目录的访问一致性进行修改。另外，操作指令也可以不携带AccessConsistencyLeve，即不指定需要修改的访问一致性，此时表示目录继承其上级对象的访问一致性。在对文件系统进行管理时，可以根据应用需求设置操作指令需要携带的参数，本申请实施例对其不做具体限定。
第六种操作：查询目录的访问一致性。作为一种示例，其操作指令可以为：Get Dir Access Consistency Level(DirID)，其中，DirID指示需要查询的目录。需要说明的是，操作指令也可以不携带DirID，即不指示目录，此时可以根据操作指令对发送操作指令的用户使用的所有目录的访问一致性进行查询。
需要说明的是，操作指令也可以携带FileSystemId，即指示文件系统，此时可以对操作指令指示的文件系统的目录的访问一致性进行查询。当操作指令不指示文件系统时，此时可以对操作指令对发送操作指令的用户当前使用文件系统的目录的访问一致性进行查询。在对文件系统进行管理时，可以根据应用需求设置操作指令需要携带的参数，本申请实施例对其不做具体限定。
第七种操作：配置文件的访问一致性。作为一种示例，其操作指令可以为：Set File Access Consistency Level(FileID，AccessConsistencyLevel)，其中，FileID指示需要配置访问一致性的文件，AccessConsistencyLevel指示需要为该文件配置的访问一致性。
需要说明的是，操作指令也可以不携带FileID，即不指示文件，此时可以根据操作指令对发送操作指令的用户使用的所有文件的访问一致性进行设置。操作指令也可以携带DirId，即指示文件所属的目录，此时可以对操作指令指示的目录下的文件的访问一致性进行设置。当操作指令不指示目录时，此时可以对操作指令对发送操作指令的用户当前使用目录下的文件的访问一致性进行设置。并且，操作指令也可以携带FileSystemId，即指示文件系统，此时可以对操作指令指示的文件系统的文件的访问一致性进行设置。当操作指令不指示文件系统时，此时可以对操作指令对发送操作指令的用户当前使用文件系统的文件的访问一致性进行设置。另外，操作指令也可以不携带AccessConsistencyLeve，即不指定需要设置的访问一致性，此时表示文件继承其上级对象的访问一致性。
第八种操作：修改文件的访问一致性。作为一种示例，其操作指令可以为：Modify File Access Consistency Level(FileID，AccessConsistencyLevel)，其中，FileID指示需要修改访问一致性的文件，AccessConsistencyLevel指示该文件修改后的访问一致性。
需要说明的是，操作指令也可以不携带FileID，即不指示文件，此时可以根据操作指令对发送操作指令的用户使用的所有文件的访问一致性进行修改。操作指令也可以携带DirId，即指示文件所属的目录，此时可以对操作指令指示的目录下的文件的访问一致性进行设置。当操作指令不指示目录时，此时可以对操作指令对发送操作指令的用户当前使用目录下的文件的访问一致性进行设置。并且，操作指令也可以携带FileSystemId，即指示文件系统，此时可以对操作指令指示的文件系统的文件的访问一致性进行修改。当操作指令不指示文件系统时，此时可以对操作指令对发送操作指令的用户当前使用文件系统的文件的访问一致性进行修改。另外，操作指令也可以不携带AccessConsistencyLeve，即不指定需要修改的访问一致性，此时表示文件继承其上级对象的访问一致性。
第九种操作：查询文件的访问一致性。作为一种示例，其操作指令可以为：Get File Access Consistency Level(FileID)，其中，FileID指示需要查询的文件。
需要说明的是，操作指令也可以不携带FileID，即不指示文件，此时可以根据操作指令对发送操作指令的用户使用的所有文件的访问一致性进行查询。操作指令也可以携带DirId，即指示文件所属的目录，此时可以对操作指令指示的目录下的文件的访问一致性进行设置。当操作指令不指示目录时，此时可以对操作指令对发送操作指令的用户当前使用目录下的文件的访问一致性进行设置。并且，操作指令也可以携带FileSystemId，即指示文件系统，此时可以对操作指令指示的文件系统的文件的访问一致性进行查询。当操作指令不指示文件系统时，此时可以对操作指令对发送操作指令的用户当前使用文件系统的文件的访问一致性进行查询。
对应于不同的应用需求，文件系统的访问一致性的实现情况可以包括多种。本申请实施例以以下几种 实现情况为例，对访问一致性的实现情况进行说明：
在第一种实现情况中，访问一致性指示：在对目标对象执行写操作后，对目标对象的读操作能够读取到执行写操作后的数据。此时，该实现情况的访问一致性可称为写后读(Read after write)，其指示对于任意文件f，客户端a对其进行了修改，那么在修改后的时间，若客户端b对文件f执行读操作，则应该读到修改后的新数值。
在第二种实现情况中，访问一致性指示：在对目标对象执行写操作，且对目标对象进行刷新后，对目标对象的读操作能够读取到执行写操作后的数据。在一种实现方式中，刷新可以通过同步操作(如sync同步)实现。此时，该实现情况的访问一致性可称为同步后读(Read after sync)，其指示对于任意文件f，客户端a对其进行了修改，那么在修改后时间，若客户端b对文件f执行读操作，需要在对文件sync同步后，才能读到修改后的新数值。
在第三种实现情况中，访问一致性指示：在对目标对象执行写操作，且重启目标对象后，对目标对象的读操作能够读取到执行写操作后的数据。在一种实现方式中，重启可以通过关闭并重新打开文件实现。此时，该实现情况的访问一致性可称为关闭后读(Read after close)，其指示对于任意文件f，客户端a对其进行了修改，那么在修改后时间，若客户端b对文件f执行读操作，需要在关闭并重新打开文件后，才能读到修改后的新数值。
需要说明的是，以上三种实现情况仅为对文件系统的访问一致性实现情况的示例性说明，并不构成对于本申请实施例涉及的文件系统具有的访问一致性的限定。本领域普通技术人员可知，随着业务需求的改变，其实现情况可以根据应用需求进行调整，本申请实施例对其不做一一列举。
步骤402、基于操作指令，对目标对象执行操作指令指示的操作。
计算机设备接收到操作指令后，就能够基于操作指令，对目标对象执行操作指令指示的操作，实现对目标对象的访问一致性的操作。
在本申请实施例中，针对文件系统的目标对象的访问一致性进行操作的功能，可以通过多种方式实现。在一种可实现方式中，可以通过调用应用程序接口(application programming interface，API)实现。例如，文件系统可以配置有用于实现其支持的所有操作的应用程序接口，计算机设备接收到操作指令后，可以调用用于实现该操作指令指示的操作的应用程序接口，以通过其实现该操作指令指示的操作。
步骤403、接收访问指令，访问指令指示对目标对象进行访问。
在使用文件系统的用户需要对文件系统的目标对象进行访问时，用户可以通过一些操作触发访问指令，以便于计算机设备能够基于该访问指令，向用户反馈其请求访问的内容。例如，当用户在使用云平台提供的文件系统云服务时，用户在基于其业务需求需要某个文件时，用户可以通过执行一些操作触发客户端向云平台发送该访问指令，以便于云平台基于该访问指令向用户反馈其请求访问的文件的内容。
步骤404、基于目标对象的访问一致性，按照对目标对象执行操作指令指示的操作后的状态，对访问指令进行响应。
计算机设备接收到访问指令后，可以获取目标对象当前的状态，并基于该状态和目标对象的访问一致性，对访问请求进行响应。例如，当访问指令为读指令时，继续以步骤401中访问一致性的三种实现情况为例进行说明。对于Read after write这种实现情况，无论访问指令请求访问的文件f当前的状态是什么，通过计算机设备对访问指令的响应，客户端均能够读到在读指令前最后一次对文件f修改的数值。对于Read after sync这种实现情况，若文件f当前的状态为在修改后未进行sync同步，通过计算机设备对访问指令的响应，客户端不能够读到在读指令前最后一次对文件f修改的数值，若文件f当前的状态为在修改后已进行sync同步，通过计算机设备对访问指令的响应，客户端才能够读到在读指令前最后一次对文件f修改的数值。对于Read after close这种实现情况，若文件f当前的状态为在修改后未关闭，通过计算机设备对访问指令的响应，客户端不能够读到在读指令前最后一次对文件f修改的数值，若文件f当前的状态为在修改后已关闭，通过计算机设备对访问指令的响应，客户端才能够读到在读指令前最后一次对文件f修改的数值。
下面以三个例子对目标对象的访问一致性的操作进行说明：
如图5所示，在创建文件系统时，用户可以通过操作触发操作指令，以指示将文件系统的访问一致性设置为level1，则计算机设备能够基于操作指令将文件系统的访问一致性设置为level1，如将文件系统的根目录的访问一致性设置为level1。在文件系统的使用过程中，用户在创建目录1、文件1、目录2和文件2 时，均未指示其访问一致性，则目录1和文件1继承其上级对象(图5中为根目录)的访问一致性level1，目录2和文件2继承其上级对象(图5中为目录1)的访问一致性level1。其中，由于目录1、文件1、目录2和文件2需要继承其上级对象的访问一致性，则需要查询对应上级对象的访问一致性。图5中对象后括号中的数字表示对象的访问一致性。
如图6所示，在创建文件系统时，用户可以通过操作触发操作指令，以指示将文件系统的访问一致性设置为level1，则计算机设备能够基于操作指令将文件系统的访问一致性设置为level1，如将文件系统的根目录的访问一致性设置为level1。在文件系统的使用过程中，用户在创建目录1、文件1和文件2时，均未指示其访问一致性，则目录1和文件1继承其上级对象(图6中为根目录)的访问一致性level1，文件2继承其上级对象(图6中为目录1)的访问一致性level1。在文件系统的使用过程中，用户在创建目录2时，指示将目录2的访问一致性配置为level2，则计算机设备将目录2的访问一致性设置为level2。在文件系统的后续使用过程中，用户指示将目录1的访问一致性配置为level3，且配置目录1的下级对象不继承目录1修改后的访问一致性，则计算机设备将目录1的访问一致性修改为level3，目录2的访问一致性保持为level2不变，文件2的访问一致性保持为level1不变。在文件系统的后续使用过程中，用户又指示在目录1下创建文件3，但未指示其访问一致性，则文件3继承其上级对象(图6中为目录1)的访问一致性level3(即修改后的访问一致性)。其中，由于目录1、文件1和文件2需要继承其上级对象的访问一致性，则需要查询对应上级对象的访问一致性。图6中对象后括号中的数字表示对象的访问一致性，箭头尾部的数字表示变更前的访问一致性，箭头头部的数字表示变更后的访问一致性。
如图7所示，在创建文件系统时，用户可以通过操作触发操作指令，以指示将文件系统的访问一致性设置为level1，则计算机设备能够基于操作指令将文件系统的访问一致性设置为level1，如将文件系统的根目录的访问一致性设置为level1。在文件系统的使用过程中，用户在创建目录1、文件1和目录2时，均未指示其访问一致性，则目录1和文件1继承其上级对象(图7中为根目录)的访问一致性level1，目录2继承其上级对象(图7中为目录1)的访问一致性level1。在文件系统的使用过程中，用户在创建文件2时，指示将目录2的访问一致性配置为level2，则计算机设备将文件2的访问一致性设置为level2。在文件系统的后续使用过程中，用户指示将文件1的访问一致性修改为level3，将文件2的访问一致性修改为level3，则计算机设备将文件1和文件2的访问一致性均修改为level3。其中，由于目录1、文件1和目录2需要继承其上级对象的访问一致性，则需要查询对应上级对象的访问一致性。图7中对象后括号中的数字表示对象的访问一致性，箭头尾部的数字表示变更前的访问一致性，箭头头部的数字表示变更后的访问一致性。
综上所述，在本申请实施例提供的文件系统的管理方法中，在文件系统处于能够被使用的状态时，计算机设备能够接收第一客户端发送的操作指令，并基于操作指令，对目标对象执行操作指令指示的操作。其中，该操作指令指示针对文件系统的目标对象的访问一致性进行操作。由于在文件系统在处于能够被使用的状态的情况下，计算机设备能够基于操作指令针对文件系统的目标对象的访问一致性进行操作，使得文件系统在设计完成后，其访问一致性还能够被改变，这样就能够便于根据不同的应用需求调整文件系统的对象的访问一致性，使得文件系统能够满足不同应用场景的应用需求，有效地提高了文件系统的可用性。
需要说明的是，本申请实施例提供的文件系统的管理方法的步骤先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减。任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本申请的保护范围之内，因此不再赘述。
本申请提供了一种文件系统的管理装置。如图8所示，该文件系统的管理装置80包括：
交互模块801，用于在文件系统处于能够被使用的状态时，接收操作指令，操作指令指示针对文件系统的目标对象的访问一致性进行操作。
处理模块802，用于基于操作指令，对目标对象执行操作指令指示的操作。
可选的，目标对象包括以下一种或多种：文件系统的根目录、目录和文件。
可选的，文件系统中不同目标对象能够配置为具有不同的访问一致性。
可选的，操作包括以下一种或多种：配置目标对象的访问一致性；修改目标对象的访问一致性；以及，查询目标对象的访问一致性。
可选的，目标对象为文件系统和/或目录时，配置目标对象的访问一致性包括以下一种或多种：配置目标对象的访问一致性，且配置目标对象的下级对象继承为目标对象配置的访问一致性；配置目标对象的访 问一致性，且配置目标对象的下级对象不继承为目标对象配置的访问一致性。
类似的，目标对象为文件系统和/或目录时，修改目标对象的访问一致性包括以下一种或多种：修改目标对象的访问一致性，且配置目标对象的下级对象继承目标对象修改后的访问一致性；以及，修改目标对象的访问一致性，且配置目标对象的下级对象不继承目标对象修改后的访问一致性。
可选的，访问一致性包括以下一种或多种：
在对目标对象执行写操作后，对目标对象的读操作能够读取到执行写操作后的数据；
在对目标对象执行写操作，且对目标对象进行刷新后，对目标对象的读操作能够读取到执行写操作后的数据；
在对目标对象执行写操作，且重启目标对象后，对目标对象的读操作能够读取到执行写操作后的数据。
可选的，交互模块801，还用于接收访问指令，访问指令指示对目标对象进行访问；处理模块802，还用于基于目标对象的访问一致性，按照对目标对象执行操作指令指示的操作后的状态，对访问指令进行响应。
综上所述，在本申请实施例提供的文件系统的管理装置中，在文件系统处于能够被使用的状态时，交互模块能够接收第一客户端发送的操作指令，处理模块能够基于操作指令，对目标对象执行操作指令指示的操作。其中，该操作指令指示针对文件系统的目标对象的访问一致性进行操作。由于在文件系统在处于能够被使用的状态的情况下，该文件系统的管理装置能够基于操作指令针对文件系统的目标对象的访问一致性进行操作，使得文件系统在设计完成后，其访问一致性还能够被改变，这样就能够便于根据不同的应用需求调整文件系统的对象的访问一致性，使得文件系统能够满足不同应用场景的应用需求，有效地提高了文件系统的可用性。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的装置和模块的具体工作过程，可以参考前述方法实施例中的对应内容，在此不再赘述。
本申请实施例提供了一种计算机设备。该计算机设备用于实现本申请实施例提供的文件系统的管理方法中的部分或全部功能。图9是本申请实施例提供的一种计算机设备的结构示意图。如图9所示，该计算机设备900包括处理器901、存储器902、通信接口903和总线904。其中，处理器901、存储器902、通信接口903通过总线904实现彼此之间的通信连接。
处理器901可以包括通用处理器和/或专用硬件芯片。通用处理器可以包括：中央处理器(central processing unit，CPU)、微处理器或图形处理器(graphics processing unit，GPU)。CPU例如是一个单核处理器(single-CPU)，又如是一个多核处理器(multi-CPU)。专用硬件芯片是一个高性能处理的硬件模块。专用硬件芯片包括数字信号处理器、专用集成电路(application-specific integrated circuit，ASIC)、现场可编程逻辑门阵列(field-programmable gate array，FPGA)或者网络处理器(network processer，NP)中的至少一项。处理器901还可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，本申请的文件系统的管理方法的部分或全部功能，可以通过处理器901中的硬件的集成逻辑电路或者软件形式的指令完成。
存储器902用于存储计算机程序，计算机程序包括操作系统902a和可执行代码(即程序指令)902b。存储器902例如是只读存储器或可存储静态信息和指令的其它类型的静态存储设备，又如是随机存取存储器或者可存储信息和指令的其它类型的动态存储设备，又如是电可擦可编程只读存储器、只读光盘或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备，或者是能够用于携带或存储具有指令或数据结构形式的期望的可执行代码并能够由计算机存取的任何其它介质，但不限于此。例如存储器902用于存放出端口队列等。存储器902例如是独立存在，并通过总线904与处理器901相连接。或者存储器902和处理器901集成在一起。存储器902可以存储可执行代码，当存储器902中存储的可执行代码被处理器901执行时，处理器901用于执行本申请实施例提供的文件系统的管理方法的部分或全部功能。处理器901执行该过程的实现方式请相应参考前述实施例中的相关描述。存储器902中还可以包括操作系统等其他运行进程所需的软件模块和数据等。
通信接口903使用例如但不限于收发器一类的收发模块，来实现与其他设备或通信网络之间的通信。例如，通信接口903可以是以下器件的任一种或任一种组合：网络接口(如以太网接口)、无线网卡等具有网络接入功能的器件。
总线904是任何类型的，用于实现计算机设备的内部器件(例如，存储器902、处理器901、通信接口903)互连的通信总线。例如系统总线。本申请实施例以计算机设备内部的上述器件通过总线904互连为例说明，可选地，计算机设备900内部的上述器件还可以采用除了总线904之外的其他连接方式彼此通信连接。例如，计算机设备900内部的上述器件通过内部的逻辑接口互连。
需要说明的是，上述多个器件可以分别设置在彼此独立的芯片上，也可以至少部分的或者全部的设置在同一块芯片上。将各个器件独立设置在不同的芯片上，还是整合设置在一个或者多个芯片上，往往取决于产品设计的需要。本申请实施例对上述器件的具体实现形式不做限定。且上述各个附图对应的流程的描述各有侧重，某个流程中没有详述的部分，可以参见其他流程的相关描述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。提供程序开发平台的计算机程序产品包括一个或多个计算机指令，在计算机设备上加载和执行这些计算机程序指令时，全部或部分地实现本申请实施例提供的文件系统的管理方法的功能。
并且，计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质存储有提供程序开发平台的计算机程序指令。
本申请实施例还提供了一种计算机集群。该计算机集群包括多个计算机设备，多个计算机设备包括多个处理器和多个存储器，多个存储器中存储有程序指令，多个处理器运行程序指令，使得计算机集群用于实现如本申请实施例提供的文件系统的管理方法的功能。其中，该计算机集群中各个计算机设备的实现方式请相应参考前述计算机设备的实现方式，此处不再赘述。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质为非易失性计算机可读存储介质，该计算机可读存储介质包括程序指令，当程序指令在计算机设备上运行时，使得计算机设备实现如本申请实施例提供的文件系统的管理方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机实现本申请实施例提供的文件系统的管理方法。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
需要说明的是，本申请所涉及的信息(包括但不限于用户设备信息、用户个人信息等)、数据(包括但不限于用于分析的数据、存储的数据、展示的数据等)以及信号，均为经用户授权或者经过各方充分授权的，且相关数据的收集、使用和处理需要遵守相关国家和地区的相关法律法规和标准。例如，本申请中涉及到的操作指令和访问指令等都是在充分授权的情况下获取的。
在本申请实施例中，术语“第一”、“第二”和“第三”仅用于描述目的，而不能理解为指示或暗示相对重要性。术语“至少一个”是指一个或多个，术语“多个”指两个或两个以上，除非另有明确的限定。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的构思和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (18)

  1. 一种文件系统的管理方法，其特征在于，所述方法包括：
    在所述文件系统处于能够被使用的状态时，接收操作指令，所述操作指令指示针对所述文件系统的目标对象的访问一致性进行操作；
    基于所述操作指令，对所述目标对象执行所述操作指令指示的操作。
  2. 如权利要求1所述的方法，其特征在于，所述目标对象包括以下一种或多种：所述文件系统的根目录、目录和文件。
  3. 如权利要求1所述的方法，其特征在于，所述文件系统中不同目标对象能够配置为具有不同的访问一致性。
  4. 如权利要求1至3任一所述的方法，其特征在于，所述操作包括以下一种或多种：
    配置所述目标对象的访问一致性；
    修改所述目标对象的访问一致性；
    以及，查询所述目标对象的访问一致性。
  5. 如权利要求4所述的方法，其特征在于，所述目标对象为所述文件系统和/或所述目录时，所述配置所述目标对象的访问一致性包括以下一种或多种：
    配置所述目标对象的访问一致性，且配置所述目标对象的下级对象继承为所述目标对象配置的访问一致性；
    配置所述目标对象的访问一致性，且配置所述目标对象的下级对象不继承为所述目标对象配置的访问一致性；
    所述目标对象为所述文件系统和/或所述目录时，所述修改所述目标对象的访问一致性包括以下一种或多种：
    修改所述目标对象的访问一致性，且配置所述目标对象的下级对象继承所述目标对象修改后的访问一致性；
    以及，修改所述目标对象的访问一致性，且配置所述目标对象的下级对象不继承所述目标对象修改后的访问一致性。
  6. 如权利要求1至3任一所述的方法，其特征在于，所述访问一致性包括以下一种或多种：
    在对所述目标对象执行写操作后，对所述目标对象的读操作能够读取到执行写操作后的数据；
    在对所述目标对象执行写操作，且对所述目标对象进行刷新后，对所述目标对象的读操作能够读取到执行写操作后的数据；
    在对所述目标对象执行写操作，且重启所述目标对象后，对所述目标对象的读操作能够读取到执行写操作后的数据。
  7. 如权利要求1至3任一所述的方法，其特征在于，在所述基于所述操作指令，对所述目标对象执行所述操作指令指示的操作之后，所述方法还包括：
    接收访问指令，所述访问指令指示对所述目标对象进行访问；
    基于所述目标对象的访问一致性，按照对所述目标对象执行所述操作指令指示的操作后的状态，对所述访问指令进行响应。
  8. 一种文件系统的管理装置，其特征在于，所述装置包括：
    交互模块，用于在所述文件系统处于能够被使用的状态时，接收操作指令，所述操作指令指示针对所 述文件系统的目标对象的访问一致性进行操作；
    处理模块，用于基于所述操作指令，对所述目标对象执行所述操作指令指示的操作。
  9. 如权利要求8所述的装置，其特征在于，所述目标对象包括以下一种或多种：所述文件系统的根目录、目录和文件。
  10. 如权利要求8所述的装置，其特征在于，所述文件系统中不同目标对象能够配置为具有不同的访问一致性。
  11. 如权利要求8至10任一所述的装置，其特征在于，所述操作包括以下一种或多种：
    配置所述目标对象的访问一致性；
    修改所述目标对象的访问一致性；
    以及，查询所述目标对象的访问一致性。
  12. 如权利要求11所述的装置，其特征在于，所述目标对象为所述文件系统和/或所述目录时，所述配置所述目标对象的访问一致性包括以下一种或多种：
    配置所述目标对象的访问一致性，且配置所述目标对象的下级对象继承为所述目标对象配置的访问一致性；
    配置所述目标对象的访问一致性，且配置所述目标对象的下级对象不继承为所述目标对象配置的访问一致性；
    所述目标对象为所述文件系统和/或所述目录时，所述修改所述目标对象的访问一致性包括以下一种或多种：
    修改所述目标对象的访问一致性，且配置所述目标对象的下级对象继承所述目标对象修改后的访问一致性；
    以及，修改所述目标对象的访问一致性，且配置所述目标对象的下级对象不继承所述目标对象修改后的访问一致性。
  13. 如权利要求8至10任一所述的装置，其特征在于，所述访问一致性包括以下一种或多种：
    在对所述目标对象执行写操作后，对所述目标对象的读操作能够读取到执行写操作后的数据；
    在对所述目标对象执行写操作，且对所述目标对象进行刷新后，对所述目标对象的读操作能够读取到执行写操作后的数据；
    在对所述目标对象执行写操作，且重启所述目标对象后，对所述目标对象的读操作能够读取到执行写操作后的数据。
  14. 如权利要求8至10任一所述的装置，其特征在于，
    所述交互模块，还用于接收访问指令，所述访问指令指示对所述目标对象进行访问；
    所述处理模块，还用于基于所述目标对象的访问一致性，按照对所述目标对象执行所述操作指令指示的操作后的状态，对所述访问指令进行响应。
  15. 一种计算机设备，其特征在于，包括存储器和处理器，所述存储器存储有程序指令，所述处理器运行所述程序指令以执行权利要求1至7任一所述的方法。
  16. 一种计算机集群，其特征在于，包括多个计算机设备，所述多个计算机设备包括多个处理器和多个存储器，所述多个存储器中存储有程序指令，所述多个处理器运行所述程序指令，使得所述计算机集群执行权利要求1至7任一所述的方法。
  17. 一种计算机可读存储介质，其特征在于，包括程序指令，当所述程序指令在计算机设备上运行时， 使得所述计算机设备执行如权利要求1至7任一所述的方法。
  18. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1至7任一所述的方法。
PCT/CN2023/104514 2022-08-18 2023-06-30 文件系统的管理方法及装置 WO2024037222A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210995892 2022-08-18
CN202210995892.8 2022-08-18
CN202211406915.3A CN117632849A (zh) 2022-08-18 2022-11-10 文件系统的管理方法及装置
CN202211406915.3 2022-11-10

Publications (1)

Publication Number Publication Date
WO2024037222A1 true WO2024037222A1 (zh) 2024-02-22

Family

ID=89940631

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/104514 WO2024037222A1 (zh) 2022-08-18 2023-06-30 文件系统的管理方法及装置

Country Status (1)

Country Link
WO (1) WO2024037222A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160070741A1 (en) * 2014-09-10 2016-03-10 Panzura, Inc. Managing the level of consistency for a file in a distributed filesystem
CN106096460A (zh) * 2015-04-30 2016-11-09 Arm 有限公司 在互连中实施数据保护
CN106375416A (zh) * 2016-08-30 2017-02-01 北京航空航天大学 分布式数据存储系统中一致性动态调整方法及装置
CN112306383A (zh) * 2019-08-02 2021-02-02 华为技术有限公司 执行作业的方法、计算节点、管理节点及计算设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160070741A1 (en) * 2014-09-10 2016-03-10 Panzura, Inc. Managing the level of consistency for a file in a distributed filesystem
CN106096460A (zh) * 2015-04-30 2016-11-09 Arm 有限公司 在互连中实施数据保护
CN106375416A (zh) * 2016-08-30 2017-02-01 北京航空航天大学 分布式数据存储系统中一致性动态调整方法及装置
CN112306383A (zh) * 2019-08-02 2021-02-02 华为技术有限公司 执行作业的方法、计算节点、管理节点及计算设备

Similar Documents

Publication Publication Date Title
US9977727B2 (en) Methods and systems for internally debugging code in an on-demand service environment
US10235047B2 (en) Memory management method, apparatus, and system
US20120054280A1 (en) Sharing Cloud Data Resources With Social Network Associates
US11915067B2 (en) Resource management method for node in kubernetes, device, and medium
US9645861B2 (en) Method and system for managing and presenting multiple application containers as a single logical container
US20140115089A1 (en) Method and apparatus for joining read requests
US11237761B2 (en) Management of multiple physical function nonvolatile memory devices
US10536559B2 (en) Blocking an interface of a redirected USB composite device
JP2020035453A (ja) Ｉ／ｏステアリングエンジンを備えるシステムオンチップ
CN112600761A (zh) 一种资源分配的方法、装置及存储介质
CN108293047B (zh) 由用户访问跨多个分布式计算网络的资源的系统和方法
CN103500108A (zh) 系统内存访问方法、节点控制器和多处理器系统
US9747135B2 (en) Multi-dimension scheduling among multiple consumers
CN117407159A (zh) 内存空间的管理方法及装置、设备、存储介质
WO2024037222A1 (zh) 文件系统的管理方法及装置
US10911371B1 (en) Policy-based allocation of provider network resources
US10223178B2 (en) Enabling WPD devices to be managed at the capability level
CN111562968B (zh) 一种实现ICS对Kata container管理的方法、装置、设备和介质
WO2021232860A1 (zh) 通信方法、装置及系统
US20190356725A1 (en) Generating client applications from service model descriptions
CN117632849A (zh) 文件系统的管理方法及装置
WO2024037223A1 (zh) 数据操作方法及装置
US20240256331A1 (en) Multi-phase provisioning
US20240214357A1 (en) Method to migrate workload between two environments and a system thereof
US20230401100A1 (en) Lcs workload in-band resource device management system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23854127

Country of ref document: EP

Kind code of ref document: A1