Re: [PATCH v4 0/8] Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Tony,

On 5/5/25 10:27 AM, Luck, Tony wrote:
>>> " Non-CPU agent RDT uses the RMID and CLOS tags in the same way that they are used for CPU agents."
>>
>> As I understand AMD uses a single specific (the highest CLOSid supported by L3)
>> CLOS that is then reserved for IO allocation. While both Intel and AMD technically
>> "uses CLOSid", it is done differently, no?
>>
>> Specifically, is this documentation introduced in patch #5 accurate for Intel?
>> +             The feature routes the I/O traffic via specific CLOSID reserved
>> +             for io_alloc feature. By configuring the CBM (Capacity Bit Mask)
>> +             for the CLOSID, users can control the L3 portions available for
>> +             I/0 traffic. The reserved CLOSID will be excluded for group creation.
> 
> No. Intel doesn't reserve a single CLOS. It allows to assign RMIDs and CLOSids
> for I/O monitoring and control. Different IDs can be assigned to different groups
> of devices (the "grouping" is dependent on h/w routing to devices, not
> assignable by the OS).

How does this work with CDP on Intel? Can CDP be enabled for CPU agents while the
"code" and "data" CLOSids be used for I/O control?

Reinette




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux