Messages in this thread | | | From | Vineeth Remanan Pillai <> | Date | Fri, 11 Oct 2019 08:10:30 -0400 | Subject | Re: [RFC PATCH v3 00/16] Core scheduling v3 |
| |
> Thanks for the clarification. > > Yes, this is the initialization issue I mentioned before when core > scheduling is initially enabled. rq1's vruntime is bumped the first time > update_core_cfs_rq_min_vruntime() is called and if there are already > some tasks queued, new tasks queued on rq1 will be starved to some extent. > > Agree that this needs fix. But we shouldn't need do this afterwards. > > So do I understand correctly that patch1 is meant to solve the > initialization issue?
I think we need this update logic even after initialization. I mean, core runqueue's min_vruntime can get updated every time when the core runqueue's min_vruntime changes with respect to the sibling's min_vruntime. So, whenever this update happens, we would need to propagate the changes down the tree right? Please let me know if I am visualizing it wrong.
Thanks, Vineeth
| |