Abstract:
A collection buffering scheme for a computer system having agents (100) of a pre-emptible bus (4) and a non-pre-emptible bus (6). An agent (110) of the non-pre-emptible bus (6), having a data width capability of N bits, when receiving a grant to write to the pre-emptible bus (4), writes instead to a collection buffer (80) capable of holding a block of more than one N bit data segments. When the collection buffer (80) is filled, the collection buffer (80) writes the entire block of data segments over the pre-emptible bus (4) to a CPU (10) or memory (60) of the computer system. Preferably, the collection buffer (80) is filled when the block size is equal to the data width capability of the pre-emptible bus (4), such that a single write to the pre-emptible bus (4) utilizes the entire capacity of the pre-emptible bus (4) in a given data transaction. Further, where the system has a CPU posting buffer (55), a system lock-up prevention negotiator is provided that drains and disables the CPU posting buffer (55) during the data transaction.
Abstract:
A method, apparatus, and system to synchronize multiple host controllers with non-uniform frame rates. The apparatus includes a first host controller, a second host controller, and logic. The first host controller is configured to access memory at a first frame rate. The second host controller is configured to access the memory at a second frame rate which is different from the first frame rate. The logic is coupled to the first and second host controllers to synchronize the memory accesses of the first and second host controllers at a common frame rate. Other embodiments are described.
Abstract:
In one embodiment, a system includes: a first root space associated with a first root space identifier and including at least one first host processor and a first agent, the at least one first host processor and the first agent associated with the first root space identifier; a second root space associated with a second root space identifier and including at least one second host processor and a second agent, the at least one second host processor and the second agent associated with the second root space identifier; and a shared fabric to couple the first root space and the second root space, the shared fabric to route a transaction to the first root space or the second root space based at least in part on a root space field of the transaction. Other embodiments are described and claimed.
Abstract:
In one embodiment, a system includes: a first root space associated with a first root space identifier and including at least one first host processor and a first agent, the at least one first host processor and the first agent associated with the first root space identifier; a second root space associated with a second root space identifier and including at least one second host processor and a second agent, the at least one second host processor and the second agent associated with the second root space identifier; and a shared fabric to couple the first root space and the second root space, the shared fabric to route a transaction to the first root space or the second root space based at least in part on a root space field of the transaction. Other embodiments are described and claimed.