CN109508304B - Memory management metadata processing method and device - Google Patents
Memory management metadata processing method and device Download PDFInfo
- Publication number
- CN109508304B CN109508304B CN201811355149.6A CN201811355149A CN109508304B CN 109508304 B CN109508304 B CN 109508304B CN 201811355149 A CN201811355149 A CN 201811355149A CN 109508304 B CN109508304 B CN 109508304B
- Authority
- CN
- China
- Prior art keywords
- memory
- memory management
- management metadata
- metadata
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000015654 memory Effects 0.000 title claims abstract description 378
- 238000003672 processing method Methods 0.000 title description 2
- 238000013507 mapping Methods 0.000 claims abstract description 55
- 238000000034 method Methods 0.000 claims abstract description 51
- 230000008569 process Effects 0.000 claims description 20
- 230000001960 triggered effect Effects 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 163
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/10—Address translation
- G06F12/1009—Address translation using page tables, e.g. page table structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/10—Address translation
- G06F12/1027—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB]
- G06F12/1036—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB] for multiple virtual address spaces, e.g. segmentation
Abstract
The embodiment of the application discloses a method and a device for processing memory management metadata, which are used for processing the memory management metadata more efficiently, and the method comprises the following steps: calling mmap to allocate a memory management metadata memory, wherein the memory management metadata memory is a large page memory of a huge page; establishing a physical address mapping table, wherein the physical address mapping table stores physical page frame numbers of the memory management metadata memory corresponding to each memory management metadata; and responding to a request for accessing the target memory management metadata, and searching a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata through a physical address mapping table to realize the access to the target memory management metadata, wherein the target memory management metadata is any memory management metadata.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for processing memory management metadata.
Background
Memory management refers to the technique of allocating and using memory resources of a device while code is running. In a storage system, a layer of memory management module is provided through a Linux kernel module on the basis of Linux-based memory management, so as to realize more flexible memory management methods such as power failure protection. In the implementation process of this method, a lot of memory management metadata are needed, and in the memory management process, the memory management metadata need to be used, and a method for effectively processing the memory management metadata is lacking in the prior art.
Disclosure of Invention
In view of this, embodiments of the present disclosure provide a method and an apparatus for processing memory management metadata, so as to implement more efficient processing of the memory management metadata.
In order to solve the above problem, the technical solution provided by the embodiment of the present application is as follows:
a method for processing memory management metadata, the method comprising:
calling mmap to allocate a memory management metadata memory, wherein the memory management metadata memory is a large page memory of a huge page;
establishing a physical address mapping table, wherein the physical address mapping table stores physical page frame numbers of the memory management metadata memory corresponding to each memory management metadata;
and responding to a request for accessing the target memory management metadata, and searching a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata through the physical address mapping table so as to access the target memory management metadata, wherein the target memory management metadata is any memory management metadata.
In one possible implementation, the invoking mmap to allocate the memory management metadata memory includes:
and starting a user-state process to call mmap to allocate the memory to manage the metadata memory.
In one possible implementation, the method further includes:
and adding a huge page memory identifier for the memory management metadata memory.
In one possible implementation, the access-target memory management metadata request is triggered when a page fault occurs.
In a possible implementation manner, the searching, by using the physical address mapping table, for a physical page frame number of the memory management metadata memory corresponding to the target memory management metadata to achieve access to the target memory management metadata includes:
searching a physical page frame number of the memory management metadata memory corresponding to the target memory management metadata through the physical address mapping table;
determining a memory physical address corresponding to the physical page frame number;
acquiring a memory virtual address corresponding to the target memory management metadata according to a mapping relation between a memory physical address and a memory virtual address;
and accessing the memory virtual address corresponding to the target memory management metadata so as to realize the access to the target memory management metadata.
A memory management metadata processing apparatus, the apparatus comprising:
the calling unit is used for calling the mmap to allocate the memory management metadata memory, and the memory management metadata memory is a large page memory of a huge page;
the device comprises a building unit, a storage unit and a processing unit, wherein the building unit is used for building a physical address mapping table, and the physical address mapping table stores physical page frame numbers of the memory management metadata memory corresponding to each memory management metadata;
and the access unit is used for responding to a request for accessing the target memory management metadata, and searching a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata through the physical address mapping table so as to access the target memory management metadata, wherein the target memory management metadata is any memory management metadata.
In a possible implementation manner, the invoking unit is specifically configured to:
and starting a user-state process to call mmap to allocate the memory to manage the metadata memory.
In one possible implementation, the apparatus further includes:
and the adding unit is used for adding a hub page memory identifier for the memory management metadata memory.
In one possible implementation, the access-target memory management metadata request is triggered when a page fault occurs.
In one possible implementation, the access unit includes:
the searching subunit is configured to search, through the physical address mapping table, a physical page frame number of the memory management metadata memory corresponding to the target memory management metadata;
the determining subunit is used for determining a memory physical address corresponding to the physical page frame number;
the obtaining subunit is configured to obtain a memory virtual address corresponding to the target memory management metadata according to a mapping relationship between a memory physical address and a memory virtual address;
and the access subunit is used for accessing the memory virtual address corresponding to the target memory management metadata so as to realize the access to the target memory management metadata.
Therefore, the embodiment of the application has the following beneficial effects:
in the embodiment of the application, the memory management metadata memory for processing the memory management metadata uses a huge page memory, so that the efficiency of accessing the memory management metadata is improved, meanwhile, in order to facilitate the kernel module to use the memory management metadata memory allocated by mmap, a physical address mapping table is added, and a physical page frame number of the memory management metadata memory corresponding to the accessed target memory management metadata is searched through the physical address mapping table, so that the target memory management metadata is quickly accessed.
Drawings
Fig. 1 is a flowchart of a method for processing memory management metadata according to an embodiment of the present disclosure;
fig. 2 is a flowchart of accessing target memory management metadata according to an embodiment of the present application;
fig. 3 is a schematic diagram illustrating accessing target memory management metadata according to an embodiment of the present application;
fig. 4 is a schematic diagram of a processing apparatus for memory management metadata according to an embodiment of the present disclosure.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, embodiments accompanying the drawings are described in detail below.
The memory management metadata is needed to be used in the memory management process, and a method for effectively processing the memory management metadata is lacked in the prior art. To this end, embodiments of the present application provide a method for processing memory management metadata in a storage system using a large page memory, and further provide a method for accessing the memory management metadata using a memory management metadata memory (the memory management metadata memory employs the large page memory). The method and the device for selecting the huge page in the embodiment of the application aim to replace a traditional 4kb memory page by using a large-page memory, so that the number of managed virtual addresses is reduced, the mapping from the virtual addresses to the physical addresses is accelerated, and the overall performance of the memory is improved by discarding the swapping-in and swapping-out of the memory page, so that the efficiency of accessing the memory management metadata is improved, and the performance of the whole storage system is improved.
The following describes in detail a method and an apparatus for processing memory management metadata according to an embodiment of the present application with reference to the drawings.
Referring to fig. 1, a flowchart illustrating a method for processing memory management metadata according to an embodiment of the present application is shown, where the method includes the following steps:
step 101: and calling mmap to allocate the memory management metadata memory, wherein the memory management metadata memory is a huge page memory.
In this embodiment, a memory management metadata memory for processing the memory management metadata needs to be allocated first, so that both a kernel module and a user-mode application of the storage system can use the memory management metadata memory.
In order to realize that the kernel module and the user-mode application can use the memory management metadata memory, mmap can be called to allocate the memory management metadata memory. The mmap is a method for mapping files in the memory. In a specific implementation, a user-mode process may be initiated to invoke mmap to allocate the memory to manage the metadata memory. Before loading the kernel module, the mmap is called to allocate the memory management metadata memory by executing a user-mode process, so that the memory management metadata memory is allocated well before loading the kernel module and can be used by one file name of mmap.
In the process of allocating and sharing the memory management metadata memory, when the mmap is called with the page memory identifier (for example, VM _ hugetl tag), it represents that the allocated memory management metadata memory needs to be the page memory. Finding an available free area in the virtual memory, allocating a virtual memory space as a memory management metadata memory, and adding a hub page memory identifier to the allocated memory management metadata memory to identify the allocated memory management metadata memory as the hub page memory. The memory management metadata memory is composed of a plurality of huge page memories.
Step 102: and establishing a physical address mapping table, wherein the physical address mapping table stores the physical page frame number of the memory management metadata memory corresponding to each memory management metadata.
In order to enable a kernel module in a storage system to conveniently use a memory distributed by a user mode through mmap, a physical address mapping table is added, physical page frame numbers of the memory management metadata memory corresponding to each memory management metadata table are stored in the physical address mapping table, and each physical page frame number corresponds to a memory physical address. In a specific implementation, the physical address mapping table may be obtained through a/proc/self/pagemap file.
For example, the memory management metadata table may include an anchor table, a bus table, a nar table, a ref table, an iob table, and the like, where each memory management metadata table corresponds to a plurality of hub page memories, and the physical address mapping table stores the physical page frame numbers of the respective hub page memories corresponding to each memory management metadata table.
Step 103: and responding to a request for accessing the target memory management metadata, and searching a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata through a physical address mapping table to realize the access to the target memory management metadata, wherein the target memory management metadata is any memory management metadata.
A request to access target memory management metadata, which may be any one of the memory management metadata, may be triggered when a page fault occurs, for example, the request to access target memory management metadata may be a request to access iob table.
In response to the request for accessing the target memory management metadata, the physical page frame number of the memory management metadata memory corresponding to the target memory management metadata can be searched through a physical address mapping table, a virtual memory address corresponding to the target memory management metadata can be obtained through the physical page frame number, and the target memory management metadata can be accessed by accessing the virtual memory address. The access process to the target memory management metadata can be seen in the detailed description of the following embodiments.
In this way, in the embodiment of the present application, the memory management metadata memory for managing the memory management metadata uses the huge page memory, so that the efficiency of accessing the memory management metadata is improved, and meanwhile, in order to facilitate the kernel module to use the memory management metadata memory allocated by mmap, a physical address mapping table is added, and a physical page frame number of the memory management metadata memory corresponding to the accessed target memory management metadata is searched through the physical address mapping table, so as to realize quick access to the target memory management metadata.
Referring to fig. 2, which shows a flowchart of a process for accessing target memory management metadata according to an embodiment of the present application, in some possible implementation manners, a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata is searched through a physical address mapping table to implement access to the target memory management metadata, where the process may include the following steps:
step 201: and searching a physical page frame number of the memory management metadata memory corresponding to the target memory management metadata through a physical address mapping table.
In this embodiment, the physical address mapping table stores the physical page frame number of the memory management metadata memory corresponding to each piece of memory management metadata, and the physical address mapping table can be searched to obtain the physical page frame number of a certain page memory corresponding to the target memory management metadata.
Step 202: and determining the memory physical address corresponding to the physical page frame number.
Each physical page frame number corresponds to a fixed physical memory address, and the physical memory address corresponding to the physical page frame number obtained in step 201 can be determined.
Step 203: and acquiring a memory virtual address corresponding to the target memory management metadata according to the mapping relation between the memory physical address and the memory virtual address.
Meanwhile, if there is a preset mapping relationship between the physical memory address and the virtual memory address, the virtual memory address corresponding to the physical memory address obtained in step 202 may be determined. The memory virtual address is the memory virtual address needed to access the target memory management metadata.
Step 204: and accessing the memory virtual address corresponding to the target memory management metadata to realize the access to the target memory management metadata.
By accessing the memory virtual address corresponding to the target memory management metadata, access to the target memory management metadata can be achieved. In addition, in practical application, the mapping process from the virtual address to the physical address can be established by accessing the target memory management metadata.
Referring to fig. 3, a schematic diagram of a process of accessing target memory management metadata according to an embodiment of the present application is shown.
In combination with the actual application scenario, taking iob table as the target memory management metadata as an example, a process of accessing the target memory management metadata will be described. Firstly, iob table sequence numbers are obtained, and according to the iob table sequence numbers, which hub page memory the iob table is in can be calculated to obtain the memory number of the hub page in which the hub page is located. If the number of the memory of the hub page is obtained, the physical page frame number of the memory of the hub page corresponding to the iob table can be searched in the physical address mapping table, that is, the corresponding physical page frame number can be searched in the physical address mapping table according to the number of the memory of the hub page corresponding to the iob table. The physical page frame number corresponds to a memory physical address, and a corresponding memory virtual address can be obtained according to the mapping relation between the memory physical address and the memory virtual address. Then accessing the memory virtual address may enable accessing the iob table.
Therefore, the embodiment of the application can realize quick access to the target memory management metadata through the set physical address mapping table.
Referring to fig. 4, a schematic diagram illustrating a memory management metadata processing apparatus according to an embodiment of the present application is shown, where the memory management metadata processing apparatus may include:
a calling unit 401, configured to call a mmap to allocate a memory management metadata memory, where the memory management metadata memory is a large page memory of a huge page;
a building unit 402, configured to build a physical address mapping table, where the physical address mapping table stores physical page frame numbers of the memory management metadata memory corresponding to each memory management metadata;
an accessing unit 403, configured to, in response to a request for accessing a target memory management metadata, search a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata through the physical address mapping table, so as to implement access to the target memory management metadata, where the target memory management metadata is any one of the memory management metadata.
In a possible implementation manner, the invoking unit may be specifically configured to:
and starting a user-state process to call mmap to allocate the memory to manage the metadata memory.
In one possible implementation, the apparatus may further include:
and the adding unit is used for adding a hub page memory identifier for the memory management metadata memory.
In one possible implementation, the access-target memory management metadata request is triggered when a page fault occurs.
In one possible implementation, the access unit may include:
the searching subunit is configured to search, through the physical address mapping table, a physical page frame number of the memory management metadata memory corresponding to the target memory management metadata;
the determining subunit is used for determining a memory physical address corresponding to the physical page frame number;
the obtaining subunit is configured to obtain a memory virtual address corresponding to the target memory management metadata according to a mapping relationship between a memory physical address and a memory virtual address;
and the access subunit is used for accessing the memory virtual address corresponding to the target memory management metadata so as to realize the access to the target memory management metadata.
In this way, in the embodiment of the present application, the memory management metadata memory for managing the memory management metadata uses the huge page memory, so that the efficiency of accessing the memory management metadata is improved, and meanwhile, in order to facilitate the kernel module to use the memory management metadata memory allocated by mmap, a physical address mapping table is added, and a physical page frame number of the memory management metadata memory corresponding to the accessed target memory management metadata is searched through the physical address mapping table, so as to realize quick access to the target memory management metadata.
It should be noted that, in the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the system or the device disclosed by the embodiment, the description is simple because the system or the device corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. A method for processing memory management metadata, the method comprising:
calling mmap to allocate a memory management metadata memory, wherein the memory management metadata memory is a large page memory of a huge page;
establishing a physical address mapping table, wherein the physical address mapping table stores physical page frame numbers of the memory management metadata memory corresponding to each memory management metadata;
in response to a request for accessing the target memory management metadata, searching a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata through the physical address mapping table;
determining a memory physical address corresponding to the physical page frame number;
acquiring a memory virtual address corresponding to the target memory management metadata according to a mapping relation between a memory physical address and a memory virtual address;
and accessing a memory virtual address corresponding to the target memory management metadata to realize the access to the target memory management metadata, wherein the target memory management metadata is any memory management metadata.
2. The method of claim 1, wherein invoking the mmap to allocate the memory management metadata memory comprises:
and starting a user-state process to call mmap to allocate the memory to manage the metadata memory.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
and adding a huge page memory identifier for the memory management metadata memory.
4. The method of claim 1, wherein the access target memory management metadata request is triggered when a page fault occurs.
5. An apparatus for processing memory management metadata, the apparatus comprising:
the calling unit is used for calling the mmap to allocate the memory management metadata memory, and the memory management metadata memory is a large page memory of a huge page;
the device comprises a building unit, a storage unit and a processing unit, wherein the building unit is used for building a physical address mapping table, and the physical address mapping table stores physical page frame numbers of the memory management metadata memory corresponding to each memory management metadata;
the access unit is used for responding to a request for accessing target memory management metadata, searching a physical page frame number of a memory management metadata memory corresponding to the target memory management metadata through the physical address mapping table so as to access the target memory management metadata, wherein the target memory management metadata is any one of the memory management metadata;
the access unit includes:
the searching subunit is configured to search, through the physical address mapping table, a physical page frame number of the memory management metadata memory corresponding to the target memory management metadata;
the determining subunit is used for determining a memory physical address corresponding to the physical page frame number;
the obtaining subunit is configured to obtain a memory virtual address corresponding to the target memory management metadata according to a mapping relationship between a memory physical address and a memory virtual address;
and the access subunit is used for accessing the memory virtual address corresponding to the target memory management metadata so as to realize the access to the target memory management metadata.
6. The apparatus according to claim 5, wherein the invoking unit is specifically configured to:
and starting a user-state process to call mmap to allocate the memory to manage the metadata memory.
7. The apparatus of claim 5 or 6, further comprising:
and the adding unit is used for adding a hub page memory identifier for the memory management metadata memory.
8. The apparatus of claim 5, wherein the access target memory management metadata request is triggered when a page fault occurs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811355149.6A CN109508304B (en) | 2018-11-14 | 2018-11-14 | Memory management metadata processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811355149.6A CN109508304B (en) | 2018-11-14 | 2018-11-14 | Memory management metadata processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109508304A CN109508304A (en) | 2019-03-22 |
| CN109508304B true CN109508304B (en) | 2021-10-29 |
Family
ID=65748480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811355149.6A Active CN109508304B (en) | 2018-11-14 | 2018-11-14 | Memory management metadata processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109508304B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110046106B (en) * | 2019-03-29 | 2021-06-29 | 海光信息技术股份有限公司 | Address translation method, address translation module and system |
| CN110008030B (en) * | 2019-04-16 | 2020-06-19 | 苏州浪潮智能科技有限公司 | Method, system and equipment for accessing metadata |
| CN110209603B (en) * | 2019-05-31 | 2021-08-31 | 龙芯中科技术股份有限公司 | Address translation method, device, equipment and computer readable storage medium |
| CN113076266B (en) * | 2021-06-04 | 2021-10-29 | 深圳华云信息系统有限公司 | Memory management method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8417873B1 (en) * | 2008-06-24 | 2013-04-09 | Virident Systems, Inc. | Random read and read/write block accessible memory |
| CN105893269A (en) * | 2016-03-31 | 2016-08-24 | 武汉虹信技术服务有限责任公司 | Memory management method used in Linux system |
| US9478274B1 (en) * | 2014-05-28 | 2016-10-25 | Emc Corporation | Methods and apparatus for multiple memory maps and multiple page caches in tiered memory |
| CN108664419A (en) * | 2018-04-03 | 2018-10-16 | 郑州云海信息技术有限公司 | A kind of method and its device of determining memory big page number |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7647471B2 (en) * | 2006-11-17 | 2010-01-12 | Sun Microsystems, Inc. | Method and system for collective file access using an mmap (memory-mapped file) |
-
2018
- 2018-11-14 CN CN201811355149.6A patent/CN109508304B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8417873B1 (en) * | 2008-06-24 | 2013-04-09 | Virident Systems, Inc. | Random read and read/write block accessible memory |
| US9478274B1 (en) * | 2014-05-28 | 2016-10-25 | Emc Corporation | Methods and apparatus for multiple memory maps and multiple page caches in tiered memory |
| CN105893269A (en) * | 2016-03-31 | 2016-08-24 | 武汉虹信技术服务有限责任公司 | Memory management method used in Linux system |
| CN108664419A (en) * | 2018-04-03 | 2018-10-16 | 郑州云海信息技术有限公司 | A kind of method and its device of determining memory big page number |
Non-Patent Citations (2)
| Title |
|---|
| A case study of 3D RTM-TTI algorithm on multicore and many-core platforms;Zhang Xiuxia 等;《HIGH TECHNOLOGY LETTERS》;20170630;第23卷(第2期);第185-190页 * |
| 基于J2EE的服务器优化技术研究与实现;龙鹏 等;《科技创新与应用》;20131231;第1-2页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109508304A (en) | 2019-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109508304B (en) | Memory management metadata processing method and device | |
| US10705965B2 (en) | Metadata loading in storage systems | |
| US10686756B2 (en) | Method and apparatus for managing MAC address generation for virtualized environments | |
| US8261267B2 (en) | Virtual machine monitor having mapping data generator for mapping virtual page of the virtual memory to a physical memory | |
| JP2019509529A5 (en) | ||
| CN105868028B (en) | Method, device and terminal for sharing data among processes | |
| JP2018022529A5 (en) | ||
| EP3185516A1 (en) | Address processing method, related device and system | |
| CN110908609B (en) | Method, system and equipment for processing disk and readable storage medium | |
| US20170220393A1 (en) | Autonomous dynamic optimization of platform resources | |
| US20070106875A1 (en) | Memory management | |
| WO2015067074A1 (en) | Data reading method and apparatus | |
| US9075634B2 (en) | Minimizing overhead in resolving operating system symbols | |
| WO2015161506A1 (en) | Method and device for addressing | |
| JP2021502637A (en) | Computer programs, computer systems and methods to facilitate processing in a computing environment | |
| US20040088498A1 (en) | System and method for preferred memory affinity | |
| CN109033365B (en) | Data processing method and related equipment | |
| JP5588072B2 (en) | Memory allocation method, program, and system | |
| US9292452B2 (en) | Identification of page sharing opportunities within large pages | |
| US8751724B2 (en) | Dynamic memory reconfiguration to delay performance overhead | |
| US11221944B1 (en) | Managing metadata for a backup data storage | |
| WO2017054636A1 (en) | Method and apparatus for processing virtual machine snapshots | |
| US20230244601A1 (en) | Computer memory management in computing devices | |
| US10817432B2 (en) | Memory address assignment method for virtual machine and apparatus | |
| US20040073907A1 (en) | Method and system of determining attributes of a functional unit in a multiple processor computer system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |