Network On Chip Cache Coherency

transcript

Final report, part B

Students: Zemer Tzach Kalifon Ethan

Instructor: Walter Isaschar

Winter 2009

AgendaGeneral concepts.

Description of the coherency protocol.

Architecture design.

Components implementation.

Simulations.

Functionality demonstration .Network On Chip - Cache Coherency 2

Network On Chip - Cache Coherency

General Concepts

General Background

Modern CPU’s are based on CMP – Chip-Multi Processor.

Improved performance is achieved by “Distribution and Parallelism”.

Cores interact by using NoC – Network on Chip.

Network On Chip - Cache Coherency 4

NoC General Diagram

NoC Characteristics

Wormhole packet routing.

Packet’s path is X-Y.

Units can communicate simultaneously.

Reduce power consumption.

Scalability.

Cache Coherency

Cache: On chip fast temporary storage.

Cache Coherency: CMP cores use only up to date data.

Traditionally, Cache Coherency achieved by central memory control unit.

Traditionally Cache Coherency

Line 1000 = X Line 1000 = XLine 1000 = Y

Problem Description

Prior Cache Coherency protocols are irrelevant – NoC doesn’t have central unit.

Adding such unit will damage both NoC’s scalability and parallelism.

Solution Requirements

High performance:Avoid “Hot Spots” and “Bottlenecks”.

Minimize resources.

Won’t affect main NoC characteristics (e.g. scalability).

Solution Basics

Memory control distribution according to memory spaces.

Placement of control units as part of the NoC.

Solution Diagram

Solution General Example

Read Miss on line 1000.CPU refer to the appropriate Controller.Controller order transfer of data.Other CPU sends the cache line.

Line 1000 = ?

Line 1000 = X

Project Goal

Design and implement Cache Coherency protocol for CMP based NoC.Implement NoC (part one).Implement Cache Coherency support for NoC (part

Coherency Protocol

General DescriptionThree types of transactions: Read, Read for

Ownership and Invalidation.Cache line’s status can be I/S/E

(Invalid/Shared/Exclusive respectively).Each cache control unit keeps journal which

determines line’s status.Requests are first addressed to the

appropriate cache control unit.16

Protocol’s Terminology

Requester.Home Node. Closest Sharer. Owner.

Read Miss: Line is Shared

(3)Data

(1)Read

Request(2)

Forward Request

(4)ACK

Write Miss: Line is Shared

(4)ACK

(3)Data

(2)Forward and Invalidation

Request

(7)Grant

Ownership

(5)Invalidation

(1)Read for

Ownership

(6)Invalidation

Design difficulties (1st example)

(2)Invalidation

Request

(5)Data

(1)Read for

Ownership

(3)Invalidation

Design difficulties (2nd example)

Request

(2)Invalidation

(3)Data

(4)ACK

(1)Read for

Ownership

Protocol’s FeaturesParallel handling of Read requests.Data is forwarded by the Closest Sharer.Transparency: any CPU which uses M/E/S/I is

supported.The protocol supports strongly consistent

processors.

Architecture

CMP Diagram

CPU Node Structure

NoC Interface

Functions as a gateway to the NoC.Packing/unpacking flits into/from NoC’s

Packets.Transmit and receive data simultaneously.

NoC Interface Structure

CPU Interface

Adapting between NoC’s Cache Coherency Protocol and the CPU.

Translating NoC’s Packets into/from FSB transactions.

CPU transactions doesn’t prevent the CPU Interface from handling the Protocol’s packets.

CPU Interface Structure

Controller Node Structure

Cache Coherency Controller

Manages the Coherency Protocol.Each CCC (Cache Coherency Controller) is

responsible for a specific set of the Memory Lines.

The Directory Table (DT) holds the status of the above Lines as well as several protocol’s information bits.

CCC Structure

DT General Structure

The DT will contain the following data for each Line:

Architecture Features

Message’s length vary according to its purpose. Reduces NoC’s congestion.

Messages carry the transaction information (reduces HW requirements).

Transaction can be blocked by memory update only (allows high parallelism).

Scalable. Network On Chip - Cache Coherency 34

CMPImplementatio

CMP Characteristics

Size of memory unit is 1 [Byte].Cache line comprise 2 memory units (can

be enlarged).Size of memory is 16 [Byte].CPU’s actions are determined by the user.

CPU Implementation

CPU Node Implementation

CCC Node Implementation

CMP Implementation

Synthesis Parameters

System PerformanceSystem’s clock frequency is 100 [MHz]. CPU’s hold-up (in cycles):

Event Line’s Status CPU Delay TotalInvalidation S 0 9Invalidation E 19 28 (M)Read Miss I 29 38 (M)Read Miss S 29 38Read Miss E 49 58 (M)

System Performance

M – Memory penalty.C – Dependant on number of CPUs.Delay in all nodes is one/two cycle. In larger systems network factor becomes

greater.Network On Chip - Cache Coherency 43

Event Line’s Status CPU Delay TotalWrite Miss I 29 38 (M)Write Miss S 29 38 (C)Write Miss E 29 38 (C)

CMPSimulations

Read Miss: Line is Shared (1)

CPU1x1 reads cache line. The appropriate line is stored in CPU0x0.

Read Miss: Line is Exclusive (1)

CPU1x1 reads for ownership. The appropriate line is stored in CPU0x0.

Demonstration

Demonstration Diagram

Tasks – Part A

Familiarize with design tools.Familiarize with VirtexII Pro FPGA

(application & components).Design & Implement NoC’s router.Assemble NoC (2x2 grid) using our router

implementation.

Tasks – Part B

Design Cache Coherency protocol for CMP based on faculty research.

Assemble CMP based on our NoC.Implement the protocol as part of the

assembled CMP.

Future Work

Memory should be distributed.Improve NoC Interface latency.Messages carry all the transaction’s

information.Strongly consistent processors.

Conclusions (1)

All architectural goals were achieved. Minimal HW utilization makes for practical

solution. The most efficient possible by protocol

definition.

Conclusions (2)

The generic design makes a great basis for further studies and research.

With larger systems, the project advantages would be even more predominant.

Network On Chip Cache Coherency

Documents