Uncore Manual

ManualsBrandsIntel ManualsOtherIntel Celeron Processor 766 MHz, 128K Cache, 66 MHz FSB

Reference Number: 329468-002 49

Uncore Performance Monitoring

Cacheing Agent (Cbo) Performance Monitoring

RxR_OCCUPANCY

• Title: Ingress Occupancy

• Category: INGRESS Events

• Event Code: 0x11

• Max. Inc/Cyc:. 20, Register Restrictions: 0

• Definition: Counts number of entries in the specified Ingress queue in each cycle.

• NOTE: IRQ_REJECTED should not be Ored with the other umasks.

TOR_INSERTS

• Title: TOR Inserts

• Category: TOR Events

• Event Code: 0x35

• Max. Inc/Cyc:. 1, Register Restrictions: 0-1

• Definition: Counts the number of entries successfully inserted into the TOR that match qualifica-

tions specified by the subevent. There are a number of subevent 'filters' but only a subset of the

subevent combinations are valid. Subevents that require an opcode or NID match require the

Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD

Local Misses, one should select “MISS_OPC_MATCH” and set Cn_MSR_PMON_BOX_FILTER.opc to

DRD (0x182).

IIO_CREDITS bxx1xxxxx No IIO Credits

Number of times a request attempted to acquire the NCS/NCB

credit for sending messages on BL to the IIO. There is a single

credit in each CBo that is shared between the NCS and NCB

message classes for sending transactions on the BL ring (such as

read data) to the IIO.

WB_CREDITS b1xxxxxxx No WB Credits

Retries of writes to local memory due to lack of HT WB credits

Table 2-32. Unit Masks for RxR_OCCUPANCY

Extension

umask

[15:8]

Description

IRQ b00000001 IRQ

IRQ_REJECTED b00000010 IRQ Rejected

IPQ b00000100 IPQ

VFIFO b00010000 VFIFO

Accumulates the number of used entries in the IRQ Ordering

FIFO in each cycle. In the prior generation uncore in Intel Xeon

processor E5-2600 Product Family, it is necessary to keep IO

requests in order. Therefore, they are allocated into an ordering

FIFO that sits next to the IRQ, and must be satisfied from the

FIFO in order (with respect to each other). This event, in

conjunction with the Allocations event, can be used to calculate

average lifetime in the FIFO. This event can be used in

conjunction with the Not Empty event to calculate average

queue occupancy. Transactions are allocated into the FIFO as

soon as they enter the Cachebo (and the IRQ) and are

deallocated from the FIFO as soon as they are deallocated from

the IRQ.

Table 2-31. Unit Masks for RxR_ISMQ_RETRY

Extension

umask

[15:8]

Description