# US 2023/0056665 A1 · Mechanism to provide reliable receipt of event messages

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0056665 A1
- Document ID: US20230056665A1
- Status: Published application
- Kind: A1
- Application number: 17/405,217
- Filed: 2021-08-18
- Published: 2023-02-23
- Earliest claimed: 2021-08-18
- Assignees: Micron Technology, Inc.
- Applicants: Micron Technology, Inc.
- Inventors: Patrick Estep; Tony M. Brewer
- Web page: https://patentgrep.com/patent/US20230056665A1

## CPC

- G06F 9/3889: {controlled by multiple instructions, e.g. MIMD, decoupled access or execute}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/30043: {LOAD or STORE instructions; Clear instruction}
- G06F 9/30076: {to perform miscellaneous control operations, e.g. NOP}
- G06F 9/3009: {Thread control instructions}
- G06F 9/3851: {from multiple instruction streams, e.g. multistreaming}
- G06F 9/522: {Barrier synchronisation}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 15/167: using a common memory, e.g. mailbox
- G06F 15/7825: {Globally asynchronous, locally synchronous, e.g. network on chip}
- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Devices and techniques for providing receipts for event messages in a processor are described herein. A system includes multiple memory-compute nodes coupled to one another over a scale fabric; a set of registers; and an event manager hardware circuitry to: receive an event message corresponding to an event, and the event associated with an event mode; track a counter value representing a number of received event messages related to the event, the counter value stored in the set of registers; compare the number of received event messages to a trigger value; and in response to the number of received event messages equaling the trigger value: use an atomic operation to reset the counter value in the set of registers while maintaining the event mode; and alert a thread of the event.

## Claims

### Claim 1

A system comprising:
multiple memory-compute nodes coupled to one another over a scale fabric, wherein each of the memory-compute nodes comprise a hybrid threading processor and a hybrid threading fabric configured to execute multiple processing threads in parallel;
a set of registers; and
an event manager hardware circuitry to:
receive an event message corresponding to an event, and the event associated with an event mode;
track a counter value representing a number of received event messages related to the event, the counter value stored in the set of registers;
compare the number of received event messages to a trigger value; and
in response to the number of received event messages equaling the trigger value:
use an atomic operation to reset the counter value in the set of registers while maintaining the event mode; and
alert a thread of the event.

### Claim 2 (depends on 1)

The system of claim 1, wherein the event message was sent from a source thread on a first memory-compute node, and wherein the thread alerted of the event is executing on a second memory-compute node that is different than the first memory-compute node.

### Claim 3 (depends on 1)

The system of claim 1, wherein the event manager hardware circuitry is to establish, based on a command issued from the thread, the event mode, wherein the command includes the trigger value.

### Claim 4 (depends on 1)

The system of claim 1, wherein the event manager hardware circuitry is to establish, based on a command issued from the thread, a destination for event messages corresponding to the event, wherein the destination is a register in the set of registers.

### Claim 5 (depends on 1)

The system of claim 1, wherein to maintain the event mode, the thread does not change the event mode.

### Claim 6 (depends on 1)

The system of claim 1, wherein the event mode is a collection mode.

### Claim 7 (depends on 1)

The system of claim 1, wherein to maintain the event mode, the thread does not transition to a simple mode and then transition to a collection mode.

### Claim 8 (depends on 1)

The system of claim 1, wherein to track the counter value, the counter value is initially set based on the trigger value and the counter value is decremented in response to receiving an event message.

### Claim 9 (depends on 1)

The system of claim 1, wherein to track the counter value, the counter value is initially set to zero and the counter value is incremented in response to receiving an event message.

### Claim 10

A method comprising:
receiving an event message corresponding to an event, the event message associated with an event mode, and the event message for event handling on a memory-compute node, the memory-compute node one of multiple memory-compute nodes coupled to one another over a scale fabric in a system, each of the memory-compute nodes comprising a hybrid threading processor and a hybrid threading fabric configured to execute multiple processing threads in parallel;
tracking a counter value representing a number of received event messages related to the event, the counter value stored in a set of registers;
comparing the number of received event messages to a trigger value; and
in response to the number of received event messages equaling the trigger value:
using an atomic operation to reset the counter value in the set of registers while maintaining the event mode; and
alerting a thread of the event.

### Claim 11 (depends on 10)

The method of claim 10, wherein the event message was sent from a source thread on a first memory-compute node, and wherein the thread alerted of the event is executing on a second memory-compute node that is different than the first memory-compute node.

### Claim 12 (depends on 10)

The method of claim 10, comprising establishing, based on a command issued from the thread, the event mode, wherein the command includes the trigger value.

### Claim 13 (depends on 10)

The method of claim 10, comprising establishing, based on a command issued from the thread, a destination for event messages corresponding to the event, wherein the destination is a register in the set of registers.

### Claim 14 (depends on 10)

The method of claim 10, wherein while maintaining the event mode, the thread does not change the event mode.

### Claim 15 (depends on 10)

The method of claim 10, wherein the event mode is a collection mode.

### Claim 16 (depends on 10)

The method of claim 10, wherein while maintaining the event mode, the thread does not transition to a simple mode and then transition to a collection mode.

### Claim 17 (depends on 10)

The method of claim 10, wherein tracking the counter value comprises initially setting the counter value based on the trigger value and decrementing the counter value in response to receiving an event message.

### Claim 18 (depends on 10)

The method of claim 10, wherein tracking the counter value comprises initially setting the counter value to zero and incrementing the counter value in response to receiving an event message.

### Claim 19

A non-transitory machine-readable medium including instructions, which when executed by a machine, cause the machine to:
receive an event message corresponding to an event, the event associated with an event mode, and the event message for event handling on a memory-compute node, the memory-compute node one of multiple memory-compute nodes coupled to one another over a scale fabric in a system, each of the memory-compute nodes comprising a hybrid threading processor and a hybrid threading fabric configured to execute multiple processing threads in parallel;
track a counter value representing a number of received event messages related to the event, the counter value stored in a set of registers;
compare the number of received event messages to a trigger value; and
in response to the number of received event messages equaling the trigger value:
use an atomic operation to reset the counter value in the set of registers while maintaining the event mode; and
alert a thread of the event.

### Claim 20 (depends on 19)

The non-transitory machine-readable medium of claim 19, wherein the event message was sent from a source thread on a first memory-compute node, and wherein the thread alerted of the event is executing on a second memory-compute node that is different than the first memory-compute node.
