Accelerating boot time zeroing of memory based on non-volatile memory (nvm) technology
US-2015378615-A1 · Dec 31, 2015 · US
US9870171B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9870171-B2 |
| Application number | US-201514883304-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 14, 2015 |
| Priority date | Jun 25, 2015 |
| Publication date | Jan 16, 2018 |
| Grant date | Jan 16, 2018 |
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.
A system includes a processor and a memory storing a program, and a computer readable medium includes a program for zeroing memory in computing systems where access to memory is non-uniform. When executed on a processor, the program causes the processor to perform an operation that includes receiving, via a system call, a request for a pool of memory. The operation also includes determining a size of the requested pool of memory, and creating a dummy memory segment. The size of the dummy memory segment is larger than the size of the requested pool of memory. The operation further includes filling the dummy memory segment with one or more pages, based on the determined size of the requested pool of memory, and deleting the dummy memory segment.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: a processor; and a memory containing a program which, when executed on the processor, performs an operation, the operation comprising: receiving, via a system call, a request for a pool of memory; determining, based on a type of the request, a size of the requested pool of memory; creating a dummy memory segment, wherein a size of the dummy memory segment is larger than the size of the requested pool of memory; filling the dummy memory segment with one or more pages, based on the determined size of the requested pool of memory; and deleting the dummy memory segment prior to allocating the one or more pages for the requested pool of memory, wherein deleting the dummy memory segment comprises zeroing the one or more pages in the dummy memory segment. 2. The system of claim 1 , wherein zeroing the one or more pages in the dummy memory segment comprises: sorting the one or more pages of the dummy memory segment according to each associated affinity domain of each page, wherein each affinity domain comprises a cluster of processors and memory local to the cluster of processors; sending requests to zero the sorted one or more pages to one or more software threads that are attached to the respective affinity domain; and waiting, after sending the requests, to return to a system caller until a message is received, from the software threads in each affinity domain, indicating that all requests to zero have been processed. 3. The system of claim 1 , wherein zeroing the one or more pages in the dummy memory segment comprises: transmitting a request to zero the one or more pages in the dummy memory segment to an intermediate software thread; using the intermediate software thread to perform the request as a background process; and upon receiving a message from the intermediate software thread, returning to a system caller, while performing the request, via the intermediate software thread, continues in the background. 4. The system of claim 1 , wherein the type of request is a request to grow the pool of memory. 5. The system of claim 4 , wherein the size of the requested pool of memory is determined based on a size that the pool of memory is requested to grow by. 6. The system of claim 1 , wherein the type of request is a request to create the pool of memory. 7. The system of claim 6 , wherein the size of the requested pool of memory is determined based on a size of the pool of memory that needs to be created. 8. A non-transitory computer-readable storage medium storing instructions, which, when executed on a processor, perform an operation, the operation comprising: receiving, via a system call, a request for a pool of memory; determining, based on a type of the request, a size of the requested pool of memory; creating a dummy memory segment, wherein a size of the dummy memory segment is larger than the size of the requested pool of memory; filling the dummy memory segment with one or more pages, based on the determined size of the requested pool of memory; and deleting the dummy memory segment prior to allocating the one or more pages for the requested pool of memory, wherein deleting the dummy memory segment comprises zeroing the one or more pages in the dummy memory segment. 9. The non-transitory computer-readable storage medium of claim 8 , wherein zeroing the one or more pages in the dummy memory segment comprises: sorting the one or more pages of the dummy memory segment according to each associated affinity domain of each page, wherein each affinity domain comprises a cluster of processors and memory local to the cluster of processors; sending requests to zero the sorted one or more pages to one or more software threads that are attached to the respective affinity domain; and waiting, after sending the requests, to return to a system caller until a message is received, from the software threads in each affinity domain, indicating that all requests to zero have been processed. 10. The non-transitory computer-readable storage medium of claim 8 , wherein zeroing the one or more pages in the dummy memory segment comprises: transmitting a request to zero the one or more pages in the dummy memory segment to an intermediate software thread; using the intermediate software thread to perform the request as a background process; and upon receiving a message from the intermediate software thread, returning to a system caller, while performing the request, via the intermediate software thread, continues in the background. 11. The non-transitory computer-readable storage medium of claim 8 , wherein the type of request is a request to grow the pool of memory. 12. The non-transitory computer-readable storage medium of claim 11 , wherein the size of the requested pool of memory is determined based on a size that the pool of memory is requested to grow by. 13. The non-transitory computer-readable storage medium of claim 8 , wherein the type of request is a request to create the pool of memory, and wherein the size of the requested pool of memory is determined based on a size of the pool of memory that needs to be created.
Free address space management · CPC title
using page tables, e.g. page table structures · CPC title
Memory management, e.g. access or allocation · CPC title
User address space allocation, e.g. contiguous or non contiguous base addressing · CPC title
the resource being the memory · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.