Jeehong Kim writes:
> On 2016년 09월 23일 01:53, bseg...@google.com wrote:
>> Jeehong Kim writes:
>>
Peter Zijlstra writes:
> You forgot to Cc Ben, who gave you feedback on v1, which is rather poor
> style. Also, I don't see how kernel-janitors is relevant to this patch.
> Th
On 2016년 09월 23일 01:53, bseg...@google.com wrote:
> Jeehong Kim writes:
>
>>> Peter Zijlstra writes:
>>>
You forgot to Cc Ben, who gave you feedback on v1, which is rather poor
style. Also, I don't see how kernel-janitors is relevant to this patch.
This is very much not a janitor
Jeehong Kim writes:
>>Peter Zijlstra writes:
>>
>>> You forgot to Cc Ben, who gave you feedback on v1, which is rather poor
>>> style. Also, I don't see how kernel-janitors is relevant to this patch.
>>> This is very much not a janitorial thing.
>>>
>>> (also, why send it twice?)
>>>
>>> On Tue,
>Peter Zijlstra writes:
>
>> You forgot to Cc Ben, who gave you feedback on v1, which is rather poor
>> style. Also, I don't see how kernel-janitors is relevant to this patch.
>> This is very much not a janitorial thing.
>>
>> (also, why send it twice?)
>>
>> On Tue, Aug 30, 2016 at 10:12:40PM +09
Peter Zijlstra writes:
> You forgot to Cc Ben, who gave you feedback on v1, which is rather poor
> style. Also, I don't see how kernel-janitors is relevant to this patch.
> This is very much not a janitorial thing.
>
> (also, why send it twice?)
>
> On Tue, Aug 30, 2016 at 10:12:40PM +0900, Jeeho
Hello,
First of all, thanks for review. And I am sorry that I forgot to CC Ben.
The reason why I sent last mail twice is that I forgot including the comments
for changes from PATCH V1.
Thanks and BR.
On 2016년 09월 01일 20:01, Peter Zijlstra wrote:
> You forgot to Cc Ben, who gave you feedback on
You forgot to Cc Ben, who gave you feedback on v1, which is rather poor
style. Also, I don't see how kernel-janitors is relevant to this patch.
This is very much not a janitorial thing.
(also, why send it twice?)
On Tue, Aug 30, 2016 at 10:12:40PM +0900, Jeehong Kim wrote:
> In case that CONFIG_
In case that CONFIG_HOTPLUG_CPU and CONFIG_CFS_BANDWIDTH is turned on
and tasks in bandwidth controlled task group run on hotplug core,
the tasks are not controlled by cfs_b->quota when hotplug core is offline
and then online. The remaining tasks in task group consume all of
cfs_b->quota on other c
In case that CONFIG_HOTPLUG_CPU and CONFIG_CFS_BANDWIDTH is turned on
and tasks in bandwidth controlled task group run on hotplug core,
the tasks are not controlled by cfs_b->quota when hotplug core is offline
and then online. The remaining tasks in task group consume all of
cfs_b->quota on other c
9 matches
Mail list logo