Scheduling processing-in-memory transactions
Scheduling processing-in-memory transactions is described. In accordance with the described techniques, a memory controller receives a transaction header from a host, where the transaction header describes a number of operations to be executed by a processing-in-memory component as part of performing the transaction. The memory controller adds the transaction header to a buffer and sends either an acknowledgement message or a negative acknowledgement message to the host, based on a current load of the processing-in-memory component. The acknowledgement message causes the host to send operations of the transaction for execution by the processing-in-memory component and the negative acknowledgement message causes the host to refrain from sending the operations of the transaction for execution by the processing-in-memory component.
1 . A system comprising:
a memory of a memory module;
a processing-in-memory component of the memory module; and
a memory controller disposed outside the memory module, the memory controller including a transaction header buffer and configured to:
receive a transaction header, from a host, for a transaction to be executed by the processing-in-memory component using data stored in the memory;
add the transaction header to the transaction header buffer; and
send an acknowledgement message to the host responsive to detecting that scheduling the transaction does not conflict with a different transaction based on information stored in the transaction header buffer; or
send a negative acknowledgment message to the host responsive to detecting that scheduling the transaction conflicts with the different transaction, based on information stored in the transaction header buffer.
2 . The system of claim 1 , wherein the transaction header describes a number of operations of the transaction to be executed by the processing-in-memory component.
3 . The system of claim 2 , wherein execution of the transaction comprises the processing-in-memory component executing the operations of the transaction sequentially without interruption.
4 . The system of claim 1 , wherein the transaction header describes priority information for the transaction.
5 . The system of claim 1 , wherein the transaction header describes one or more addresses in the memory at which the data stored in the memory is located.
6 . The system of claim 1 , wherein the transaction header describes a task identifier associated with the transaction and a source identifier associated with the host.
7 . The system of claim 1 , wherein the transaction header buffer comprises a buffer maintained at the memory controller.
8 . The system of claim 1 , wherein the transaction header buffer comprises a buffer maintained in the memory of the memory module.
9 . The system of claim 1 , wherein the memory controller is implemented in the host and the transaction header is received from a core of the host.
10 . The system of claim 1 , wherein the acknowledgement message causes the host to send operations of the transaction to the memory controller for routing to the processing-in-memory component.
11 . The system of claim 1 , wherein the acknowledgement message causes the host to send operations of the transaction directly to the processing-in-memory component.
12 . The system of claim 1 , wherein the memory controller is configured to send the acknowledgement message to the host in response to identifying that the processing-in-memory component is not scheduled to execute one or more operations using data stored in memory at an address associated with the transaction.
13 . The system of claim 1 , wherein the memory controller is configured to send the acknowledgment message to the host in response to identifying that an operation queue of the processing-in-memory component has space to queue operations of the transaction.
14 . The system of claim 1 , wherein the memory controller is configured to send the negative acknowledgment message to the host with a retry interval that indicates an amount of time to wait before subsequently requesting that the transaction be executed by the processing-in-memory component.
15 . The system of claim 14 , wherein the memory controller is configured to compute the retry interval based on a load described by one or more transaction headers maintained in the transaction header buffer.
16 . The system of claim 14 , wherein the memory controller is configured to compute the retry interval based on a load described by one or more transaction operations enqueued in an operation queue of the processing-in-memory component.
17 . The system of claim 1 , wherein the negative acknowledgement message causes the host to refrain from sending operations of the transaction for execution by the processing-in-memory component until receiving a subsequent acknowledgement message from the memory controller.
18 . The system of claim 1 , wherein the acknowledgement message causes the host to send operations of the transaction for execution by the processing-in-memory component without locking one or more locations in the memory of the memory module.
19 . A method comprising:
receiving, at a memory controller disposed outside a memory module and from a host processing device, a transaction header for a transaction to be executed by a processing-in-memory component of the memory module, the transaction header describing a number of operations involved in executing the transaction;
maintaining, by the memory controller, the transaction header in a buffer of the memory controller; and
sending, by the memory controller, an acknowledgment message to the host processing device responsive to determining, based on the transaction header maintained in the buffer of the memory controller, that a number of open spaces in an operation queue of the processing-in-memory component can fit the number of operations involved in executing the transaction.
20 . A system comprising:
a memory of a memory module;
a processing-in-memory component of the memory module; and
a memory controller disposed outside the memory module, the memory controller configured to:
receive a transaction header, from a host, for a transaction to be executed by the processing-in-memory component using data stored in the memory and add the transaction header to a transaction header buffer;
compute a retry interval based on a current load of the processing-in-memory component; and
send a negative acknowledgement message to the host that includes the retry interval in response to detecting that scheduling the transaction conflicts with a different transaction, based on information stored in the transaction header buffer.