[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2ad5f754-e0f1-899c-b7e4-0f35f47fd50b@intel.com>
Date: Wed, 19 Apr 2023 09:11:15 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Peter Newman <peternewman@...gle.com>
CC: <fenghua.yu@...el.com>, <Babu.Moger@....com>, <bp@...en8.de>,
<dave.hansen@...ux.intel.com>, <eranian@...gle.com>,
<gupasani@...gle.com>, <hpa@...or.com>, <james.morse@....com>,
<linux-kernel@...r.kernel.org>, <mingo@...hat.com>,
<skodak@...gle.com>, <tglx@...utronix.de>, <tony.luck@...el.com>,
<x86@...nel.org>
Subject: Re: [PATCH v5 2/3] x86/resctrl: Implement rename op for mon groups
Hi Peter,
On 4/19/2023 2:38 AM, Peter Newman wrote:
> On Tue, Apr 18, 2023 at 11:53 PM Reinette Chatre
> <reinette.chatre@...el.com> wrote:
>> On 3/30/2023 6:55 AM, Peter Newman wrote:
>>> If a container manager is additionally tracking containers' bandwidth
>>> usage by placing tasks from each into their own monitoring group, it
>>
>> The above sentence seems to be missing something after the "for each".
>> It seems to still parse if "for each" is removed.
>
> Did you mean "from each"?
I did, yes. Thanks for converting it to what I intended to write.
> In any case, I'll further disambiguate to
> this in my next update:
>
> "If the container manager is using monitoring groups to separately
> track the bandwidth of containers assigned to the same control group,
> it must first move the container's tasks to the default monitoring
> group of the new control group before it can move these tasks into the
> container's replacement monitoring groups under the destination
> control group."
Looks good to me. Thank you.
Reinette
Powered by blists - more mailing lists