17962401. DUAL PERSONALITY MEMORY FOR AUTONOMOUS MULTI-TENANT CLOUD ENVIRONMENT simplified abstract (Oracle International Corporation)

From WikiPatents
Revision as of 03:49, 16 April 2024 by Wikipatents (talk | contribs) (Creating a new page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

DUAL PERSONALITY MEMORY FOR AUTONOMOUS MULTI-TENANT CLOUD ENVIRONMENT

Organization Name

Oracle International Corporation

Inventor(s)

NAGARAJAN Muthukrishnan of San Ramon CA (US)

WILLIAM HENRY BENJAMIN Habeck of Eagle ID (US)

ROSHNI Chatterjee of Fremont CA (US)

SUE-KYOUNG Lee of Emerald Hills CA (US)

RAVI SHANKAR Thammaiah of Redwood Shores CA (US)

SUMANTA Chatterjee of Menlo Park CA (US)

DUAL PERSONALITY MEMORY FOR AUTONOMOUS MULTI-TENANT CLOUD ENVIRONMENT - A simplified explanation of the abstract

This abstract first appeared for US patent application 17962401 titled 'DUAL PERSONALITY MEMORY FOR AUTONOMOUS MULTI-TENANT CLOUD ENVIRONMENT

Simplified Explanation

A computing device is configured to allocate memory for exclusive use of an execution entity from both a shared memory area and a private memory area of the device. Specifically, the shared memory area is configured with a united memory pool (UMP) component. The UMP component provides portions of huge page-based memory to execution entities for exclusive use. Memory granules allocated to the UMP component are divided into smaller memory chunks, which can be allocated for exclusive use of an execution entity. These memory chunks are mapped to virtual address spaces of the assigned execution entities, allowing for dynamic adjustment of available memory for private data.

  • The computing device allocates memory for exclusive use of an execution entity from shared and private memory areas.
  • The shared memory area includes a united memory pool (UMP) component for providing huge page-based memory to execution entities.
  • Memory granules allocated to the UMP component are divided into smaller memory chunks for exclusive use by execution entities.
  • Memory chunks are mapped to virtual address spaces of assigned execution entities, allowing for dynamic adjustment of available memory for private data.

Potential Applications

This technology can be applied in:

  • High-performance computing systems
  • Virtualization environments
  • Data centers

Problems Solved

  • Efficient memory allocation for execution entities
  • Dynamic adjustment of available memory for private data
  • Improved performance in memory-intensive applications

Benefits

  • Enhanced memory management
  • Increased performance and scalability
  • Flexibility in memory allocation

Potential Commercial Applications

Optimizing memory allocation in:

  • Cloud computing services
  • Big data analytics platforms
  • High-frequency trading systems

Possible Prior Art

Prior art may include:

  • Memory management techniques in operating systems
  • Virtual memory systems in computing devices

Unanswered Questions

How does this technology impact energy consumption in computing devices?

This article does not address the potential impact of this technology on energy consumption in computing devices. Further research is needed to determine if there are any energy efficiency benefits associated with this memory allocation method.

What are the security implications of allocating memory for exclusive use of execution entities?

The article does not discuss the security implications of allocating memory for exclusive use of execution entities. It is important to investigate potential security risks and safeguards when implementing this memory allocation approach.


Original Abstract Submitted

A computing device is configured to allocate memory for exclusive use of an execution entity from both a shared memory area and a private memory area of the device. Specifically, the shared memory area is configured with a united memory pool (UMP) component. The UMP component is configured to provide portions of huge page-based memory to execution entities for exclusive use of the execution entities. Memory granules that are allocated to the UMP component are divided into smaller memory chunks (which are smaller than a huge page), each of which can be allocated for exclusive use of an execution entity. These memory chunks are mapped to virtual address spaces of the assigned execution entities. Because memory granules can be allocated to, and deallocated from, the UMP component at run-time, the amount of memory that is available for private data generated by execution entities is able to be dynamically adjusted.