mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 21:34:54 +03:00
resctrl: Do not rewrite default MB values for new allocations
The code did it "just in case" the allocation was not reset for new subdirectories. That might've happened in the past with CAT settings, but checking it now it is properly reset to its maximum values for each new CLOSID (Class of Service ID). The advantage of this is that we do not rewrite the value with itself which causes an issue with the current linux kernel and mba_MBps option where the default is UINT_MAX (or (uint32_t) -1), but gets rounded up to bandwidth granularity (10), overflows and small number (4) is set instead. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
parent
ebc4580a5f
commit
4b68c7e55b
@ -2158,9 +2158,6 @@ virResctrlAllocAssign(virResctrlInfo *resctrl,
|
||||
if (virResctrlAllocCopyMasks(alloc, alloc_default) < 0)
|
||||
return -1;
|
||||
|
||||
if (virResctrlAllocCopyMemBW(alloc, alloc_default) < 0)
|
||||
return -1;
|
||||
|
||||
for (level = 0; level < alloc->nlevels; level++) {
|
||||
virResctrlAllocPerLevel *a_level = alloc->levels[level];
|
||||
virResctrlAllocPerLevel *f_level = NULL;
|
||||
|
Loading…
Reference in New Issue
Block a user