lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176369324779.72695.12138694029606864511.b4-ty@linux.ibm.com>
Date: Fri, 21 Nov 2025 08:24:06 +0530
From: Madhavan Srinivasan <maddy@...ux.ibm.com>
To: linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        Michael Ellerman <mpe@...erman.id.au>,
        Nicholas Piggin <npiggin@...il.com>,
        Christophe Leroy <christophe.leroy@...roup.eu>,
        Naveen N Rao <naveen@...nel.org>,
        Srikar Dronamraju <srikar@...ux.ibm.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
        Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
        Tyrel Datwyler <tyreld@...ux.ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pseries/lparcfg: Add resource group monitoring

On Wed, 16 Jul 2025 16:15:56 +0530, Srikar Dronamraju wrote:
> Systems can now be partitioned into resource groups. By default all
> systems will be part of default resource group. Once a resource group is
> created, and resources allocated to the resource group, those resources
> will be removed from the default resource group. If a LPAR moved to a
> resource group, then it can only use resources in the resource group.
> 
> So maximum processors that can be allocated to a LPAR can be equal or
> smaller than the resources in the resource group.
> 
> [...]

Applied to powerpc/next.

[1/1] pseries/lparcfg: Add resource group monitoring
      https://git.kernel.org/powerpc/c/8127c4fdf169465b631b62f7e45a042ced32dc77

Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ