On Sun, 2019-10-06 at 20:05 +0200, Jürgen Groß wrote: > On 04.10.19 18:09, George Dunlap wrote: > > > > I can think of a couple of options: > > > > 1. Have schedule.c call s->tick_* when switching to / from idle > > > > 2. Get rid of s->tick_*, and have sched_credit.c suspend / resume > > ticks > > when switching to / from idle in csched_schedule() > > > > 3. Have schedule.c suspend / resume ticks, and have an interface > > that > > allows schedulers to enable / disable them. > > > > 4. Rework sched_credit to be tickless. > > I'm going with 2., as it will have multiple advantages: > Good choice! For these reasons:
> - not very intrusive > - keeps credit specifics in credit > And also because, if you'd go for 4, I'm sure that reviewing something like that would would cause me nightmares! :-O Thanks and Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
