Skip to content
0:00 / 0:00

#millcpu#thebelt#registerrenaming

The Mill CPU Architecture - the Belt (2 of 13)

Mill Computing, Inc.

1.3K subscribers • 2 videos on Hallway

YouTube
  • Recommended by 1 person: 1 on Hacker News.
  • Presented by Ivan Godard
  • Made by the vendor. The company whose product it covers made or sponsored it.

Advanced. Deep dive for people who know the field.

37K views13 years ago1 recommendation

HardwareSystems programmingCPUs and computer architecturePerformance and optimization

An in-depth presentation on the Mill CPU's 'Belt' architecture, an operand-passing model that replaces general-purpose registers to avoid register renaming.

Please share via this link: MillComputing.com/docs/belt/   01   The Belt - a new machine model   02   Two architectures   05   Why huge cost in both power and price?   06   Our result - rough numbers   09   33 MIMD operations per cycle peak   10   33 operations per cycle peak ??? Why?   11   33 operations per cycle peak ??? How?   13   The problem - lots of producers and consumers   17   The cost - and performance limit   23   Why renames?   26   What are the temps used for?   27   Split the uses   29   What you really want...   30   We call it the Belt - like a conveyer belt   32   Multiple operation issue   33   Multiple operation retire   34   Belt addressing - temporal addressing   36   Use it or lose it   37   The scratchpad   38   Single operation with multiple results   39   Function calls   40   Belt save/restore   42   Functional unit pipelines - 64 sources vs 450   43   Wide issue   44   Exposed pipeline   47   In-flight over call   49   Interrupts, traps and faults   50   Data forwarding   51   Belt timing   52   Retiring ops of different latencies   54   Belt data location   57   Summary   60   Want more?                Questions                end                fin

Why it's here

1 person recommends this, 1 disputes it

What people say. Recommended for its fascinating and detailed look at an alternative CPU architecture that replaces registers with a temporal belt.

wood_spiriton Hacker News • Recommends

On “Clockhands: Rename-Free Instruction Set Architecture for Out-of-Order Processors”

This is reminiscent of the Mill CPU which had temporal addressing and called the history a “belt”. the Mill was described in an excellent series of talks: link to this video

riazrizvion Hacker News • Disputes

On “Mill Computing in 2017”

According to the CTO, 80% of software operations are loops ( link to this video )? I need convincing of that before I watch the rest of the talk. I suspect it would be a fundamental premise for the architecture of the chip. If it's not true, the stats are probably skewed for an unusual benchmark.

mtrimpeon Hacker News • Mentions

On “Smalltalk runtime in the browser”

The Mill CPU 1 that was discussed a while ago is quite close to being the perfect architecture for a Lisp though, so hopefully many of other parts of these ideas will also come back in even more impressive forms. 1 link to this video

brigadeon Hacker News • Mentions

On “Why Registers Are Fast and RAM Is Slow”

…between higher frequencies, multiple cores, and the other effects of a context switch dominating (effective flush of l1 cache and predictors). The interesting bits nowadays are that load/store is expensive power-wise, which was what ARM identified as the major motivation behind having 32 registers (fewer spills in functions) and OoOe designs. 1 link to this video…

runekson Hacker News • Mentions

On “64-bit Linux Return-Oriented Programming”

How far has development come with the Mill CPU? This video1 mentions that "nothing with pins on the bottom" has been made yet. 1 link to this video

w0000ton Hacker News • Mentions

On “What's new in CPUs since the 80s and how does it affect programmers?”

No ordinary registers. Instead you have a FIFO queue( belt ), where every element( register ) is accessible and has a relative address( offset ). link to this video

w0000ton Hacker News • Mentions

On “What's new in CPUs since the 80s and how does it affect programmers?”

False. Mill does not do register renaming. ( Or use "lies". I failed to comprehend you second sentence. ) Here is a talk from one of the designers explaining how it is done: link to this video