mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Naveen N Rao <naveen@kernel.org>,
	Srikar Dronamraju <srikar@linux.ibm.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"Tyrel Datwyler" <tyreld@linux.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pseries/lparcfg: Add resource group monitoring
Date: Fri, 21 Nov 2025 08:24:06 +0530	[thread overview]
Message-ID: <176369324779.72695.12138694029606864511.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20250716104600.59102-1-srikar@linux.ibm.com>

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

  parent reply	other threads:[~2025-11-21  2:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 10:45 Srikar Dronamraju
2025-08-01 13:57 ` Shrikanth Hegde
2025-08-05  5:43   ` Srikar Dronamraju
2025-08-06 14:19     ` Shrikanth Hegde
2025-08-07  7:04       ` Srikar Dronamraju
2025-08-04  7:01 ` Venkat
2025-11-21  2:54 ` Madhavan Srinivasan [this message]
2025-07-29  9:21 Venkat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=176369324779.72695.12138694029606864511.b4-ty@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=naveen@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=srikar@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=tyreld@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®