Uncore Manual

Reference Number: 329468-002 107
Uncore Performance Monitoring
IRP Performance Monitoring
• Definition: Counts the number of cycles when the BL Ingress is full. This queue is where the IRP
receives data from R2PCIe (the ring). It is used for data returns from read requests as well as
outbound MMIO writes.
RxR_BL_NCS_INSERTS
• Title: BL Ingress Occupancy - NCS
• Category: BL_INGRESS_NCS Events
• Event Code: 0x03
• Max. Inc/Cyc:. 1, Register Restrictions: 0-1
• Definition: Counts the number of allocations into the BL Ingress. This queue is where the IRP
receives data from R2PCIe (the ring). It is used for data returns from read requests as well as
outbound MMIO writes.
RxR_BL_NCS_OCCUPANCY
• Title:
• Category: BL_INGRESS_NCS Events
• Event Code: 0x09
• Max. Inc/Cyc:. 24, Register Restrictions: 0-1
• Definition: Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the
IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as
outbound MMIO writes.
TICKLES
• Title: Tickle Count
• Category: TICKLES Events
• Event Code: 0x16
• Max. Inc/Cyc:. 1, Register Restrictions: 0-1
• Definition: Counts the number of tickles that are received. This is for both explicit (from Cbo)
and implicit (internal conflict) tickles.
TRANSACTIONS
• Title: Inbound Transaction Count
• Category: TRANSACTIONS Events
• Event Code: 0x15
• Max. Inc/Cyc:. 1, Register Restrictions: 0-1
• Definition: Counts the number of “Inbound” transactions from the IRP to the Uncore. This can be
filtered based on request type in addition to the source queue. Note the special filtering equation.
We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualifica-
tion based on the source portID.
Table 2-116. Unit Masks for TICKLES
Extension
umask
[15:8]
Description
LOST_OWNERSHIP bxxxxxxx1 Ownership Lost
Tracks the number of requests that lost ownership as a result of
a tickle. When a tickle comes in, if the request is not at the head
of the queue in the switch, then that request as well as any
requests behind it in the switch queue will lose ownership and
have to re-acquire it later when they get to the head of the
queue. This will therefore track the number of requests that lost
ownership and not just the number of tickles.
TOP_OF_QUEUE bxxxxxx1x Data Returned
Tracks the number of cases when a tickle was received but the
requests was at the head of the queue in the switch. In this
case, data is returned rather than releasing ownership.