Processor Namespace Management via Mentor Layer Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer processor architectures face limitations in exploiting increased transistor counts due to the 'ILP Wall' and 'Memory Wall,' primarily due to namespace management issues in register machines, which hinder parallelism and efficiency, especially in handling shared variables and memory access.

Innovation Solution

A multi-layer processor architecture is introduced, featuring a mentor layer that manages variables and their caches, and a frames/bins structure for local high-speed memory, allowing efficient operand access and parallel operations by mapping logical variables to physical memory locations, thereby overcoming namespace limitations and improving parallelism.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If register architecture namespace management is used, then operand access is simplified, but parallelism is hindered due to namespace interference

Engineering Contradiction:
Improveoperand accessVSAvoidparallelism
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The processor architecture is segmented into multiple independent layers: the instruction layer (ILP) handles parallel instruction execution, while the mentor layer (MLP) independently manages operand access and namespace mapping. This segmentation allows both instruction-level parallelism and efficient operand access to occur simultaneously without interference, as each layer operates autonomously in its own control domain.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple functional unit copies are added to increase performance, then computing capacity increases, but system complexity increases due to shadow register structures

Engineering Contradiction:
Improvecomputing capacityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The mentor layer acts as an intermediary between the instruction layer and the physical register/memory structures. Instead of requiring complex shadow register structures to manage multiple functional units, the mentor layer independently manages operand access, namespace mapping, and data flow to multiple functional units. This intermediary approach simplifies the overall system architecture while maintaining high computing capacity through parallel functional unit operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If memory size is increased to access more data, then data availability improves, but access speed decreases due to multi-chip interconnects

Engineering Contradiction:
Improvememory sizeVSAvoidaccess speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The architecture introduces a hierarchical memory organization with local high-speed memory (registers and cache) organized in a frames/bins structure, and global memory accessed through the mentor layer. This dimensional organization allows frequently accessed operands to reside in fast local memory while less frequently accessed data remains in larger global memory, achieving both high access speed for critical operations and large total memory capacity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Productivity

If instruction level parallelism is increased, then throughput improves, but the ILP wall is reached due to namespace management limitations

Engineering Contradiction:
ImprovethroughputVSAvoidnamespace complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The namespace management functions are extracted from the traditional instruction execution path and placed in the separate mentor layer. The instruction layer focuses purely on issuing parallel instructions, while the mentor layer independently handles all namespace management including register allocation, operand mapping, and data dependency resolution. This extraction removes namespace complexity as a bottleneck to instruction-level parallelism, allowing higher throughput without proportional increases in namespace management complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10140122B2Computer processor with operand/variable-mapped namespace
Publication Date: 2018.11.27 POTASH HANAN
  • US10140122B2 patent drawing
  • US10140122B2 patent drawing
  • US10140122B2 patent drawing

AI summary

A computer processor includes an operands-mapped namespace and/or a Variables mapped namespace. In some embodiments, a system for performing computing operations includes a processor comprising a namespace; and one or more memory devices physically or logically connected to the processor, wherein the memory devices comprise memory space. The namespace of the processor is not limited to the memory space of the one or more memory devices. In an embodiment, a method of computing includes physically or logically connecting a processor to one or more memory devices comprising memory space, and implementing, by the processor, a namespace, in which the namespace is not limited to the memory space to which the memory space is physically or logically connected.