Messages in this thread | | | From | Aubrey Li <> | Date | Tue, 23 Jul 2019 10:52:07 +0800 | Subject | Re: [RFC PATCH v3 00/16] Core scheduling v3 |
| |
On Mon, Jul 22, 2019 at 6:43 PM Aaron Lu <aaron.lu@linux.alibaba.com> wrote: > > On 2019/7/22 18:26, Aubrey Li wrote: > > The granularity period of util_avg seems too large to decide task priority > > during pick_task(), at least it is in my case, cfs_prio_less() always picked > > core max task, so pick_task() eventually picked idle, which causes this change > > not very helpful for my case. > > > > <idle>-0 [057] dN.. 83.716973: __schedule: max: sysbench/2578 > > ffff889050f68600 > > <idle>-0 [057] dN.. 83.716974: __schedule: > > (swapper/5/0;140,0,0) ?< (mysqld/2511;119,1042118143,0) > > <idle>-0 [057] dN.. 83.716975: __schedule: > > (sysbench/2578;119,96449836,0) ?< (mysqld/2511;119,1042118143,0) > > <idle>-0 [057] dN.. 83.716975: cfs_prio_less: picked > > sysbench/2578 util_avg: 20 527 -507 <======= here=== > > <idle>-0 [057] dN.. 83.716976: __schedule: pick_task cookie > > pick swapper/5/0 ffff889050f68600 > > Can you share your setup of the test? I would like to try it locally.
My setup is a co-location of AVX512 tasks(gemmbench) and non-AVX512 tasks (sysbench MYSQL). Let me simply it and send offline.
Thanks, -Aubrey
| |