On Tue, 1 Aug 2017, Thomas Gleixner wrote:
On Tue, 25 Jul 2017, Vikas Shivappa wrote:
Hardware uses RMID(Resource monitoring ID) to keep track of each of the
RDT events associated with tasks. The number of RMIDs is dependent on
the SKU and is enumerated via CPUID. We add support to manage
On Tue, 1 Aug 2017, Thomas Gleixner wrote:
On Tue, 25 Jul 2017, Vikas Shivappa wrote:
Hardware uses RMID(Resource monitoring ID) to keep track of each of the
RDT events associated with tasks. The number of RMIDs is dependent on
the SKU and is enumerated via CPUID. We add support to manage
On Tue, 25 Jul 2017, Vikas Shivappa wrote:
> Hardware uses RMID(Resource monitoring ID) to keep track of each of the
> RDT events associated with tasks. The number of RMIDs is dependent on
> the SKU and is enumerated via CPUID. We add support to manage the RMIDs
> which include managing the RMID
On Tue, 25 Jul 2017, Vikas Shivappa wrote:
> Hardware uses RMID(Resource monitoring ID) to keep track of each of the
> RDT events associated with tasks. The number of RMIDs is dependent on
> the SKU and is enumerated via CPUID. We add support to manage the RMIDs
> which include managing the RMID
Hardware uses RMID(Resource monitoring ID) to keep track of each of the
RDT events associated with tasks. The number of RMIDs is dependent on
the SKU and is enumerated via CPUID. We add support to manage the RMIDs
which include managing the RMID allocation and reading LLC occupancy
for an RMID.
Hardware uses RMID(Resource monitoring ID) to keep track of each of the
RDT events associated with tasks. The number of RMIDs is dependent on
the SKU and is enumerated via CPUID. We add support to manage the RMIDs
which include managing the RMID allocation and reading LLC occupancy
for an RMID.
6 matches
Mail list logo