Shared filesystem metadata caching
US-2020250092-A1 · Aug 6, 2020 · US
US2023066840A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2023066840-A1 |
| Application number | US-202117793915-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jan 27, 2021 |
| Priority date | Jan 30, 2020 |
| Publication date | Mar 2, 2023 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Using metadata for a contentless file to provide a guest context access to file content. Within a guest context, a file system is mounted from a container image which lacks a first file's content and which includes metadata defining properties of the first file and mapping data defining information for identifying a second file within another filesystem from which the first file's content is obtainable Based on the properties, a filesystem operation involving the first file is performed without switching to a host context, and a requested access to the first file's content is responded to. Responding includes, based on the mapping data, communicating a request for the host context to supply the first file's content and, after returning from a context switch, responding to the requested access by supplying content of the second file from guest memory page(s) which are mapped to host memory page(s) containing the second file's content.
Opening claim text (preview).
1 - 15 . (canceled) 16 . A method, implemented at a computer system that includes at least one processor, for using metadata for a contentless file to provide a guest context access to file content, the method comprising: within a guest context at the computer system: mounting a first filesystem namespace from a container image that includes (i) metadata defining one or more filesystem properties of a first file contained within the first filesystem namespace, the container image lacking content of the first file; and (ii) mapping data that includes information usable to identify a second file within a second filesystem namespace that is external to the guest context, and from which the content of the first file is obtainable; based on the one or more filesystem properties of the first file, performing a filesystem operation involving the first file without switching to a host context at the computer system; and based on the one or more filesystem properties of the first file, responding to a requested access to the content of the first file, including: based on the mapping data, communicating, to the host context, a request for the host context to supply the content of the first file to the guest context; and after returning from a context switch to the host context, responding to the requested access based at least on supplying content of the second file from one or more guest context memory pages, the one or more guest context memory pages mapped to one or more host context memory pages containing the content of the second file. 17 . The method of claim 16 comprising, within the host context: based on receiving the request from the guest context, identifying the second file within the second filesystem namespace; and based on identifying the second file within the second filesystem namespace, performing at least one of: identifying a mapping between the one or more host context memory pages and the one or more guest context memory pages, and configuring the one or more host context memory pages to contain the content of the second file; or mapping the one or more host context memory pages to the one or more guest context memory pages, and configuring the one or more host context memory pages to contain the content of the second file. 18 . The method of claim 16 , wherein the guest context mounting the first filesystem namespace from the container image comprises the guest context reserving the one or more guest context memory pages for accessing the first file, wherein the guest context communicating the request for access to file content of the second file to the host context comprises the guest context initiating a page fault on the one or more guest context memory pages upon an attempted access to the first file, and wherein the host context identifying the second file within the second filesystem namespace is based on the mapping data. 19 . The method of claim 16 , wherein the guest context communicating the request for access to the file content of the second file to the host context comprises the guest context sending a message to the host context, the message including the information usable to identify the second file within the second filesystem namespace. 20 . The method of claim 19 , wherein the guest context sending the message to the host context comprises the guest context performing at least one of: calling an application programming interface (API) of a network filesystem; or calling an API of a container management system. 21 . The method of claim 16 , wherein the information usable to identify the second file within the second filesystem namespace comprises at least one of a path within the second filesystem namespace, a file name identifier within the second filesystem namespace, a hash based on the second file, or a file record within the second filesystem namespace. 22 . The method of claim 16 , wherein the second filesystem namespace is accessed by the host context from a source external to the computer system. 23 . The method of claim 22 , wherein the one or more host context memory pages are filled with the file content of the second file by remote direct memory access. 24 . The method of claim 16 , wherein the guest context is a virtual address backed virtual machine, wherein the one or more guest context memory pages are guest physical memory pages, and wherein the one or more host context memory pages are at least one of host physical memory pages or host virtual memory pages. 25 . A computer system that includes at least one processor and a computer readable media having stored thereon computer-executable instructions that are executable by the at least one processor to cause the computer system to perform a method for using metadata for a contentless file to provide a guest context access to file content, the method comprising, within a guest context at the computer system: mounting a first filesystem namespace from a container image that includes (i) metadata defining one or more filesystem properties of a first file contained within the first filesystem namespace, the container image lacking content of the first file; and (ii) mapping data that includes information usable to identify a second file within a second filesystem namespace that is external to the guest context, and from which the content of the first file is obtainable; based on the one or more filesystem properties of the first file, performing a filesystem operation involving the first file without switching to a host context at the computer system; and based on the one or more filesystem properties of the first file, responding to a requested access to the content of the first file, including: based on the mapping data, communicating, to the host context, a request for the host context to supply the content of the first file to the guest context; and after returning from a context switch to the host context, responding to the requested access based at least on supplying content of the second file from one or more guest context memory pages, the one or more guest context memory pages mapped to one or more host context memory pages containing the content of the second file. 26 . The computer system of claim 25 , further comprising, within the host context: based on receiving the request from the guest context, identifying the second file within the second filesystem namespace; and based on identifying the second file within the second filesystem namespace, performing at least one of: identifying a mapping between the one or more host context memory pages and the one or more guest context memory pages, and configuring the one or more host context memory pages to contain the content of the second file; or mapping the one or more host context memory pages to the one or more guest context memory pages, and configuring the one or more host context memory pages to contain the content of the second file. 27 . The computer system of claim 25 , further comprising reserving the one or more guest context memory pages for accessing the content of the first file, and wherein communicating the request for the host context to supply the content of the first file to the guest context comprises initiating a page fault on the one or more guest context memory pages upon an attempted access to the content of the first file. 28 . The computer system of claim 25 , wherein communicating the request for the host context to supply the content of the first file to the guest context comprises the guest context sending a message to the host context, the message including the information usable to identify the second file within the second filesyst
Memory management, e.g. access or allocation · CPC title
File search processing · CPC title
Virtual file systems · CPC title
to assure secure storage of data (address-based protection against unauthorised use of memory G06F12/14; record carriers for use with machines and with at least a part designed to carry digital markings G06K19/00) · CPC title
Hypervisors; Virtual machine monitors · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.