Hi PeterZ,
I just got this in my inbox and noticed I didn't adress it to anyone. I
meant to address it to you.
On Fri, Sep 29 2017 at 17:05, Brendan Jackman wrote:
> There has been a bit of discussion on this RFC, but before I do any
> more work I'd really like your input on the basic idea.
>
>
Hi PeterZ,
I just got this in my inbox and noticed I didn't adress it to anyone. I
meant to address it to you.
On Fri, Sep 29 2017 at 17:05, Brendan Jackman wrote:
> There has been a bit of discussion on this RFC, but before I do any
> more work I'd really like your input on the basic idea.
>
>
There has been a bit of discussion on this RFC, but before I do any
more work I'd really like your input on the basic idea.
Does the approach of feeding outside info like wake_q length into the
scheduler's decisions seem basically acceptable?
Cheers,
Brendan
On Fri, Aug 11 2017 at 09:45,
There has been a bit of discussion on this RFC, but before I do any
more work I'd really like your input on the basic idea.
Does the approach of feeding outside info like wake_q length into the
scheduler's decisions seem basically acceptable?
Cheers,
Brendan
On Fri, Aug 11 2017 at 09:45,
On 09/21/2017 12:50 AM, Joel Fernandes wrote:
On Wed, Sep 20, 2017 at 2:17 PM, Atish Patra wrote:
On 09/20/2017 03:23 PM, Joel Fernandes wrote:
On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
wrote:
On Wed, Sep 20 2017 at 05:06, Joel
On 09/21/2017 12:50 AM, Joel Fernandes wrote:
On Wed, Sep 20, 2017 at 2:17 PM, Atish Patra wrote:
On 09/20/2017 03:23 PM, Joel Fernandes wrote:
On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
wrote:
On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
On Tue, Sep 19, 2017 at 3:05 AM,
On Wed, Sep 20, 2017 at 2:17 PM, Atish Patra wrote:
> On 09/20/2017 03:23 PM, Joel Fernandes wrote:
>>
>> On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
>> wrote:
>>>
>>>
>>> On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
>
> On
On Wed, Sep 20, 2017 at 2:17 PM, Atish Patra wrote:
> On 09/20/2017 03:23 PM, Joel Fernandes wrote:
>>
>> On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
>> wrote:
>>>
>>>
>>> On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
>
> On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
>
On 09/20/2017 03:23 PM, Joel Fernandes wrote:
On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
wrote:
On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
wrote:
On Mon, Sep 18 2017 at 22:15,
On 09/20/2017 03:23 PM, Joel Fernandes wrote:
On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
wrote:
On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
wrote:
On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
[..]
IIUC, if
On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
wrote:
>
> On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
>>> On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
>>> wrote:
On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
>> [..]
On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman
wrote:
>
> On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
>>> On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
>>> wrote:
On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
>> [..]
>> IIUC, if wake_affine() behaves correctly this
On 08/11/2017 04:45 AM, Brendan Jackman wrote:
This patch adds a parameter to select_task_rq, sibling_count_hint
allowing the caller, where it has this information, to inform the
sched_class the number of tasks that are being woken up as part of
the same event.
The wake_q mechanism is one case
On 08/11/2017 04:45 AM, Brendan Jackman wrote:
This patch adds a parameter to select_task_rq, sibling_count_hint
allowing the caller, where it has this information, to inform the
sched_class the number of tasks that are being woken up as part of
the same event.
The wake_q mechanism is one case
Hi Joel,
Sorry I didn't see your comments on the code before, I think it's
orthoganal to the other thread about the overall design so I'll just
respond here.
On Tue, Sep 19 2017 at 05:15, Joel Fernandes wrote:
> Hi Brendan,
>
> On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
[snip]
>>
>> diff
Hi Joel,
Sorry I didn't see your comments on the code before, I think it's
orthoganal to the other thread about the overall design so I'll just
respond here.
On Tue, Sep 19 2017 at 05:15, Joel Fernandes wrote:
> Hi Brendan,
>
> On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
[snip]
>>
>> diff
On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
>> On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
>> wrote:
>>> On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
> [..]
> IIUC, if wake_affine() behaves correctly this trick wouldn't be
> necessary on SMP
On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote:
>> On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
>> wrote:
>>> On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
> [..]
> IIUC, if wake_affine() behaves correctly this trick wouldn't be
> necessary on SMP systems, so it might be
> On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
> wrote:
>> On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
[..]
IIUC, if wake_affine() behaves correctly this trick wouldn't be
necessary on SMP systems, so it might be best guarded by the presence
>>>
>>>
> On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
> wrote:
>> On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
[..]
IIUC, if wake_affine() behaves correctly this trick wouldn't be
necessary on SMP systems, so it might be best guarded by the presence
>>>
>>> Actually wake_affine
On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
wrote:
> On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
>> Hi Brendan,
> Hi Joel,
>
> Thanks for taking a look :)
>
>> On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
>> wrote:
>>> This patch
On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman
wrote:
> On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
>> Hi Brendan,
> Hi Joel,
>
> Thanks for taking a look :)
>
>> On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
>> wrote:
>>> This patch adds a parameter to select_task_rq,
On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
> Hi Brendan,
Hi Joel,
Thanks for taking a look :)
> On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
> wrote:
>> This patch adds a parameter to select_task_rq, sibling_count_hint
>> allowing the caller, where it has
On Mon, Sep 18 2017 at 22:15, Joel Fernandes wrote:
> Hi Brendan,
Hi Joel,
Thanks for taking a look :)
> On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
> wrote:
>> This patch adds a parameter to select_task_rq, sibling_count_hint
>> allowing the caller, where it has this information, to
Hi Brendan,
On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
wrote:
> This patch adds a parameter to select_task_rq, sibling_count_hint
> allowing the caller, where it has this information, to inform the
> sched_class the number of tasks that are being woken up as part
Hi Brendan,
On Fri, Aug 11, 2017 at 2:45 AM, Brendan Jackman
wrote:
> This patch adds a parameter to select_task_rq, sibling_count_hint
> allowing the caller, where it has this information, to inform the
> sched_class the number of tasks that are being woken up as part of
> the same event.
>
>
This patch adds a parameter to select_task_rq, sibling_count_hint
allowing the caller, where it has this information, to inform the
sched_class the number of tasks that are being woken up as part of
the same event.
The wake_q mechanism is one case where this information is available.
This patch adds a parameter to select_task_rq, sibling_count_hint
allowing the caller, where it has this information, to inform the
sched_class the number of tasks that are being woken up as part of
the same event.
The wake_q mechanism is one case where this information is available.
28 matches
Mail list logo