Patent Application
20160077851
The disclosed subject matter relates generally to a virtualized file system interface and, more particularly, to a system and method for optimizing data operations over such interface. A virtual machine (VM) is a software implementation of a machine (i.e., a computer) that executes programs like a physical machine would. Generally, access to resources in virtualized environments is associated with a high level of overhead because the VM typically cannot directly communicate with a virtualized resource. A hypervisor that hosts the VM typically has the burden of emulating the needed interface or driver on behalf of the VM. In other words, the hypervisor presents the VM with a virtual platform and monitors the execution of the VM and how the VM accesses the available hardware resources.
For example, for a VM to read or write data to a virtualized storage device, control of the read or write operations will have to be transferred between the VM and the hypervisor. The hypervisor may use any type of storage interface for storing the VM's data, including local file system, network file system, network block device, etc. In a purely emulated case, the VM has no knowledge that the provided interface (i.e., the block device) is not a real physical device, because the hypervisor emulates the interface in software. A high overhead is associated with such emulation. The operational overhead is even more costly, if there is a need for transferring control intermittently between the VM and the hypervisor during I/O operations.
Embodiments of the present invention disclose a method, computer program product, and system for optimizing read operations to a storage device in a virtualized computing environment. A read system call is received by a virtual machine's (VM) operating system from an application running on the VM for data on a storage device. The VM is hosted by a hypervisor providing access to the storage device in a virtualized computing environment. A virtual file system (VFS) supported by the operating system is caused to call on a first para-virtualized file system (PVFS FE) supported by the operating system to execute the read operation. In response to determining by the PVS FE that the data to be read exists in a data cache of the PVFS FE, executing by the PVS FE the read operation from the cache of the PVFS FE.
In another aspect, in response to determining by the PVS FE that the data to be read does not exist in the data cache of the PVFS FE, passing, by the PVFS FE, the read operation to a second para-virtualized file system (PVFS BE) supported by the hypervisor, and executing by the PVS BE the read operation from a cache of the PVFS BE if the data to be read exists in the data cache of the PVFS BE, or executing, by the PVS BE, the read operation from the storage device if the data to be read does not exist in the data cache of the PVFS BE. The data to be read is then returned by the PVFS BE to the VFS.
In another aspect, in response to determining by the PVS FE that the data to be read does not exist in the data cache of the PVFS FE, passing, by the PVFS FE, the read operation to a second para-virtualized file system (PVFS BE) supported by the hypervisor, and executing by the PVS BE the read operation from a cache of the PVFS BE if the data to be read exists in the data cache of the PVFS BE, or executing, by the PVS BE, the read operation from the storage device if the data to be read does not exist in the data cache of the PVFS BE. The memory pages used by the PVFS BE to satisfy the read operation are returned to the PVFS FE by the PVFS FE. The PVFS FE writes the memory pages to its data cache, and the PVFS FE returns the data to be read to the VFS.
Features, elements, and aspects that are referenced by the same numerals in different figures represent the same, equivalent, or similar features, elements, or aspects, in accordance with one or more embodiments.
In the following, numerous specific details are set forth to provide a thorough description of various embodiments. Certain embodiments may be practiced without these specific details or with some variations in detail. In some instances, certain features are described in less detail so as not to obscure other aspects. The level of detail associated with each of the elements or features should not be construed to qualify the novelty or importance of one feature over the others.
Referring to
When the VM 105 uses a para-virtualized component (e.g., a block driver) the performance may be optimized by batching multiple I/O requests and using shared memory to avoid multiple data copies, as provided in further detail below. As shown in
In one implementation, the PVFS FE 140 and the PVFS BE 160 are utilized to allow VM 105 to perform read/write operations on storage device 180 such that the write operations are performed by way of asynchronous communication between VM 105 and hypervisor 100 and the read operations are performed by way of file system level requests. It is noteworthy that the VM's 105 memory (not shown) is desirably fully accessible from the hypervisor 100. In accordance with one embodiment, a para-virtualized file system is implemented differently from a typical file system in that the para-virtualized file system is aware that it is running in VM 105 and not directly on hardware, and uses the virtual machine's specific properties to provide additional functionality. For example, here the PVFS FE 140 and PVFS BE 160 utilize shared memory to improve performance. A typical file system (e.g., NTFS, ext3) running in VM 105 is agnostic to the fact that it is running in a virtual environment.
For example, device assignment option may be utilized to allow the VM 105 access storage device 180. A device assignment grants the VM 105, desirably, full access to storage device 180 so that the VM 105 may send I/O requests directly to storage device 180. Interrupts may be routed through the hypervisor 100. Device assignment option may not be desirable if storage device 180 is intended for sharing among several VMs and the hypervisor and may not support VM migration due to the VM's direct interface assignment to a particular device, instead of the hypervisor provided interface. It is noteworthy that in the following, the term data may refer to either content data or metadata corresponding to such data, or both. In this context, metadata may be data that provides additional information about the content data, such as directory listings, inodes, or indirect blocks, without limitation.
Referring to
In accordance with one embodiment, since the PVFS FE 140 resides in the VM's operating environment, PVFS FE 140 shares the VM's memory to temporarily cache the data that is to be written to storage device 180. On the other hand, since PVFS BE 160 resides in the hypervisor's 100 operating environment, and the hypervisor 100 has access to VM's 105 memory, then PVFS BE 160 also has access to VM's 105 memory.
In one implementation, the PVFS BE 160 asynchronously scans the VM's 105 memory to determine if any data or metadata that has been stored in the memory needs to be written to storage device 180, and, if so, PVFS BE 160 writes that data to storage device 180 (S240). The PVFS BE 160 then marks the respective data in the VM's 105 memory to indicate that said data has been written to storage device 180 (250). The asynchronous scanning may be performed based on the passage of a time interval from the last scan or determining that a certain amount of data has been written to VM's 105 memory or determining that a certain number of writes has been performed to the VM's 105 memory by the PVFS FE 140 after the last scan.
In certain embodiments, more advanced algorithms for predicting the VM's behavior may be utilized to determine the nature and frequency of VM's memory scans. For example, PVFS BE 160 or other scanning utility may monitor and model PVFS FE's 140 write patterns to predict when VM memory should be scanned. Or recent write history to the storage device 180 may be used to determine how often the VM's memory should be scanned.
Referring to
If the data to be read exists in PVFS FE's 140 cache (S340), then PVFS FE 140 attempts to satisfy the read request from its cache and executes the read operation (S370). However, if a cache miss is encountered (e.g., if the target data or the corresponding metadata is not in PVFS FE's 140 cache), PVFS FE 140 passes the original read operation to PVFS BE 160 (S350). Desirably, PVFS BE 160 executes the read operation (S360), either entirely from PVFS BE's 160 cache or from the storage device 180, if the data or the corresponding metadata are not present in PVFS BE's 160 cache.
In accordance with one embodiment, the PVFS BE 160 returns the memory pages it used to satisfy the request to the PVFS FE 140 so that PVFS FE 140 can populate its cache, and so that PVFS FE 140 may return the requested data to the VFS 120. It is noteworthy that in certain implementations the returned memory pages include the target data or the corresponding metadata or both.
Accordingly, in one or more embodiments, the hypervisor 100 is configured to have access to at least a portion of the VM's 105 memory. To perform certain I/O operations or file system modifications such as creating a file or writing to a file, the VM 105 modifies its in-memory file system state. The in-memory file system state includes data and corresponding metadata. The metadata may define the file system structure or provide additional information about a directory or a file in the file system. The PVFS BE 160 desirably asynchronously monitors the VM's 105 in-memory file system state and performs the proper write operations to commit the VM's modifications to storage device 180.
As such, in case of a write operation, the interface between PVFS FE 140 and PVFS BE 160 is asynchronous implemented, so that the VM 105 won't have to request for hypervisor 100 to control the write operation on the VM's behalf by way of a fully emulated or para-virtualized I/O interface. The PVFS BE's 160 asynchronous monitoring of the VM's 105 memory may result in the more efficient use of CPU power in contrast to implementations that require synchronous monitoring. In some implementations, the monitoring may be limited to one pass every few seconds, for example.
To avoid several switches (i.e., control transfers) between hypervisor 100 and VM 105 during a data or meta-data read operation, a single file system level read operation is utilized to service several disk block read requests. A single file system level read operation is a high-level VFS call, which is generally similar to a system call (e.g., reading from a file, reading file metadata, listing directory contents, etc.). It is noteworthy that in certain implementations no differentiation is made between data and metadata reads. To avoid servicing several disk block requests to read metadata in order to find the target data, followed by several requests to read the target data itself, the PVFS FE 140 is implemented to send a file system level request to the PVFS BE 160.
The PVFS BE 160, in one embodiment, simulates the read operation to determine the storage device's 180 segments that the PVFS FE 140 will need in order to fulfill the PVFS BE 160 read request. The PVFS BE 160 may retrieve the necessary segments from its cache or from storage device 180, and then transfers the data segments to the VM 105 together, so that the PVFS FE 140 may satisfy the read request from its cache.
The above implementation reduces the number of intermittent control switches that may be needed between the VM 105 operating system and the hypervisor 100, if the data segments were to be cached individually. The elimination of multiple switches improves read performance. In certain exemplary embodiments (e.g., NFSv4), a network file system protocol's compound operations may be utilized to implement the above configuration where a lookup and read request may be transferred from a client to the server via a single remote procedure call (e.g., RPC). In one embodiment, the hypervisor 100 provides the VM 105 with the information VM 105 needs to populate its cache and execute the operation itself. Future VM 105 read operations may thus be satisfied from cache without a need for a control switch back to the hypervisor 100.
In certain embodiments, the above system may be implemented as a para-virtualized file system in a kernel based virtual machine (KVM) hypervisor. KVM includes a notification based protocol that supports a shared memory mechanism between a VM 105 and a hypervisor 100. For the hypervisor 100 to efficiently track writes that the VM 105 performs to memory, a para-virtualized file system may be implemented on a log-structured file system (e.g., LFS or NILFS). In such exemplary log-structured file systems, data and metadata writes are appended to a log.
LFS divides a storage device into segments, wherein one of the segments is active at any one time. Each segment has a header called a summary block. Each summary block contains a pointer to the next summary block, linking segments into a chain that LFS treats as a linear log. Due to the nature of the log which supports append-only data writes, for example, the hypervisor 100 may efficiently detect writes performed by VM 105. For example, if a file meta-data update is necessary, the PVFS FE 140 will append the operation to the log. PVFS BE 160 will then monitor the log for new appends instead of monitoring all data structures of PVFS FE 140 to detect updates.
In different embodiments, the claimed subject matter may be implemented as a combination of both hardware and software elements, or alternatively either entirely in the form of hardware or entirely in the form of software. Further, computing systems and program software disclosed herein may comprise a controlled computing environment that may be presented in terms of hardware components or logic code executed to perform methods and processes that achieve the results contemplated herein. Said methods and processes, when performed by a general purpose computing system or machine, convert the general purpose machine to a specific purpose machine.
Referring to
Referring to
A computer readable storage medium may be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor medium, system, apparatus or device. The computer readable storage medium may also be implemented in a propagation medium, without limitation, to the extent that such implementation is deemed statutory subject matter. Examples of a computer readable storage medium may include a semiconductor or solid-state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk, an optical disk, or a carrier wave, where appropriate. Current examples of optical disks include compact disk, read only memory (CD-ROM), compact disk read/write (CD-R/W), digital video disk (DVD), high definition video disk (HD-DVD) or Blue-ray™ disk.
In one embodiment, processor 1101 loads executable code from storage media 1106 to local memory 1102. Cache memory 1104 optimizes processing time by providing temporary storage that helps reduce the number of times code is loaded for execution. One or more user interface devices 1105 (e.g., keyboard, pointing device, etc.) and a display screen 1107 may be coupled to the other elements in the hardware environment 1110 either directly or through an intervening I/O controller 1103, for example. A communication interface unit 1108, such as a network adapter, may be provided to enable the hardware environment 1110 to communicate with local or remotely located computing systems, printers and storage devices via intervening private or public networks (e.g., the Internet). Wired or wireless modems and Ethernet cards are a few of the exemplary types of network adapters.
It is noteworthy that hardware environment 1110, in certain implementations, may not include some or all the above components, or may comprise additional components to provide supplemental functionality or utility. Depending on the contemplated use and configuration, hardware environment 1110 may be a desktop or a laptop computer, or other computing device optionally embodied in an embedded system such as a set-top box, a personal digital assistant (PDA), a personal media player, a mobile communication unit (e.g., a wireless phone), or other similar hardware platforms that have information processing or data storage capabilities.
In some embodiments, communication interface 1108 acts as a data communication port to provide means of communication with one or more computing systems by sending and receiving digital, electrical, electromagnetic or optical signals that carry analog or digital data streams representing various types of information, including program code. The communication may be established by way of a local or a remote network, or alternatively by way of transmission over the air or other medium, including without limitation propagation over a carrier wave.
As provided here, the disclosed software elements that are executed on the illustrated hardware elements are defined according to logical or functional relationships that are exemplary in nature. It should be noted, however, that the respective methods that are implemented by way of said exemplary software elements may be also encoded in said hardware elements by way of configured and programmed processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) and digital signal processors (DSPs), for example.
Referring to
In other words, application software 1122 may be implemented as program code embedded in a computer program product in form of a computer-usable or computer readable storage medium that provides program code for use by, or in connection with, a computer or any instruction execution system. Moreover, application software 1122 may comprise one or more computer programs that are executed on top of system software 1121 after being loaded from storage media 1106 into local memory 1102. In a client-server architecture, application software 1122 may comprise client software and server software. For example, in one embodiment, client software may be executed on a client computing system that is distinct and separable from a server computing system on which server software is executed.
Software environment 1120 may also comprise browser software 1126 for accessing data available over local or remote computing networks. Further, software environment 1120 may comprise a user interface 1124 (e.g., a graphical user interface (GUI)) for receiving user commands and data. It is worthy to repeat that the hardware and software architectures and environments described above are for purposes of example. As such, one or more embodiments may be implemented over any type of system architecture, functional or logical platform or processing environment.
It should also be understood that the logic code, programs, modules, processes, methods and the order in which the respective processes of each method are performed are purely exemplary. Depending on implementation, the processes or any underlying sub-processes and methods may be performed in any order or concurrently, unless indicated otherwise in the present disclosure. Further, unless stated otherwise with specificity, the definition of logic code within the context of this disclosure is not related or limited to any particular programming language, and may comprise one or more modules that may be executed on one or more processors in distributed, non-distributed, single or multiprocessing environments.
As will be appreciated by one skilled in the art, a software embodiment may include firmware, resident software, micro-code, etc. Certain components including software or hardware or combining software and hardware aspects may generally be referred to herein as a “circuit,” “module” or “system.”
The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
Based on the foregoing, a computer system, method, and computer program product have been disclosed. However, numerous modifications and substitutions can be made without deviating from the scope of the present invention. Therefore, the present invention has been disclosed by way of example and not limitation.
This application is a continuation of, and claims the benefit of priority of, U.S. patent application Ser. No. 12/838,508, filed Jul. 19, 2010, which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12838508 | Jul 2010 | US |
| Child | 14948606 | US |
