mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Peter Newman <peternewman@google.com>, <fenghua.yu@intel.com>
Cc: <Babu.Moger@amd.com>, <bp@alien8.de>,
	<dave.hansen@linux.intel.com>, <eranian@google.com>,
	<gupasani@google.com>, <hpa@zytor.com>, <james.morse@arm.com>,
	<linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
	<skodak@google.com>, <tglx@linutronix.de>, <tony.luck@intel.com>,
	<x86@kernel.org>
Subject: Re: [PATCH v5 3/3] Documentation/x86: Documentation for MON group move feature
Date: Tue, 18 Apr 2023 14:53:23 -0700	[thread overview]
Message-ID: <c33a2f01-b439-9533-79ee-76456eabf08d@intel.com> (raw)
In-Reply-To: <20230330135558.1019658-4-peternewman@google.com>

Hi Peter,

On 3/30/2023 6:55 AM, Peter Newman wrote:
> Describe new support for moving MON groups to a new parent CTRL_MON
> group and its restrictions.
> 
> Signed-off-by: Peter Newman <peternewman@google.com>
> ---
>  Documentation/x86/resctrl.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/x86/resctrl.rst b/Documentation/x86/resctrl.rst
> index 387ccbcb558f..cb05d90111b4 100644
> --- a/Documentation/x86/resctrl.rst
> +++ b/Documentation/x86/resctrl.rst
> @@ -287,6 +287,13 @@ Removing a directory will move all tasks and cpus owned by the group it
>  represents to the parent. Removing one of the created CTRL_MON groups
>  will automatically remove all MON groups below it.
>  
> +Moving MON group directories to a new parent CTRL_MON group is supported
> +for the purpose of changing the resource allocations of a MON group
> +without impacting its monitoring data or assigned tasks. This operation
> +is not allowed for MON groups which monitor CPUs. No other move
> +operation is currently allowed other than simply renaming a CTRL_MON or
> +MON group.
> +
>  All groups contain the following files:
>  
>  "tasks":

Thank you.

Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>

Reinette

      parent reply	other threads:[~2023-04-18 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 13:55 [PATCH v5 0/3] Subject: x86/resctrl: Implement rename to help move containers' tasks Peter Newman
2023-03-30 13:55 ` [PATCH v5 1/3] x86/resctrl: Factor rdtgroup lock for multi-file ops Peter Newman
2023-03-30 13:55 ` [PATCH v5 2/3] x86/resctrl: Implement rename op for mon groups Peter Newman
2023-04-18 21:52   ` Reinette Chatre
2023-04-19  9:38     ` Peter Newman
2023-04-19 16:11       ` Reinette Chatre
2023-03-30 13:55 ` [PATCH v5 3/3] Documentation/x86: Documentation for MON group move feature Peter Newman
2023-03-30 17:33   ` Moger, Babu
2023-03-31  8:12     ` Peter Newman
2023-03-31 20:51       ` Moger, Babu
2023-04-18 21:53   ` Reinette Chatre [this message]

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=c33a2f01-b439-9533-79ee-76456eabf08d@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=Babu.Moger@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=eranian@google.com \
    --cc=fenghua.yu@intel.com \
    --cc=gupasani@google.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peternewman@google.com \
    --cc=skodak@google.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /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®