forked from Minki/linux
29b6bd41ee
Early Intel hardware implementations of Memory Bandwidth Allocation (MBA) could only control bandwidth at the processor core level. This meant that when two processes with different bandwidth allocations ran simultaneously on the same core the hardware had to resolve this difference. It did so by applying the higher throttling value (lower bandwidth) to both processes. Newer implementations can apply different throttling values to each thread on a core. Introduce a new resctrl file, "thread_throttle_mode", on Intel systems that shows to the user how throttling values are allocated, per-core or per-thread. On systems that support per-core throttling, the file will display "max". On newer systems that support per-thread throttling, the file will display "per-thread". AMD confirmed in [1] that AMD bandwidth allocation is already at thread level but that the AMD implementation does not use a memory delay throttle mode. So to avoid confusion the thread throttling mode would be UNDEFINED on AMD systems and the "thread_throttle_mode" file will not be visible. Originally-by: Reinette Chatre <reinette.chatre@intel.com> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Reinette Chatre <reinette.chatre@intel.com> Link: https://lkml.kernel.org/r/1598296281-127595-3-git-send-email-fenghua.yu@intel.com Link: [1] https://lore.kernel.org/lkml/18d277fd-6523-319c-d560-66b63ff606b8@amd.com |
||
|---|---|---|
| .. | ||
| i386 | ||
| x86_64 | ||
| amd-memory-encryption.rst | ||
| boot.rst | ||
| earlyprintk.rst | ||
| entry_64.rst | ||
| exception-tables.rst | ||
| index.rst | ||
| intel_txt.rst | ||
| intel-iommu.rst | ||
| kernel-stacks.rst | ||
| mds.rst | ||
| microcode.rst | ||
| mtrr.rst | ||
| orc-unwinder.rst | ||
| pat.rst | ||
| pti.rst | ||
| resctrl_ui.rst | ||
| tlb.rst | ||
| topology.rst | ||
| tsx_async_abort.rst | ||
| usb-legacy-support.rst | ||
| zero-page.rst | ||