lkml.org 
[lkml]   [2013]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] sched: wakeup buddy
On 03/12/2013 04:48 PM, Ingo Molnar wrote:
[snip]
>>>
>>> Instrumentation/stats/profiling will also double check the correctness of
>>> this data: if developers/users start relying on the work metric as a
>>> substitute benchmark number, then app writers will have an additional
>>> incentive to make them correct.
>>
>> I see, I could not figure out how to wisely using the info currently,
>> but I have the feeling that it will make scheduler very different ;-)
>>
>> May be we could implement the API and get those info ready firstly
>> (along with the new sched-pipe which provide work tick info), then think
>> about the way to use them in scheduler, is there any patches on the way?
>
> Absolutely.
>
> Beyond the new prctl no new API is needed: a perf soft event could be
> added, and/or a tracepoint. Then perf stat and perf record could be used
> with it. 'perf bench' could be extended to generate the work tick in its
> 'perf bench sched ...' workloads - and for 'perf bench mem numa' as well.

Nice :)

>
> vsyscall-accelerating it could be a separate, more complex step: it needs
> a per thread writable vsyscall data area to make the overhead to
> applications near zero. Performance critical apps won't call an extra
> syscall.

If it's really bring benefit, I think they will consider about it,
whatever, that's the developer/users decision, what we need to do is
just make the stuff attractively.

Regards,
Michael Wang

>
> Thanks,
>
> Ingo
>



\
 
 \ /
  Last update: 2013-03-12 11:21    [W:0.158 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site