Re: [patch] sched: skip updating rq's next_balance under null SD

* Siddha, Suresh B <[EMAIL PROTECTED]> wrote: > Was playing with sched_smt_power_savings/sched_mc_power_savings and > found out that while the scheduler domains are reconstructed when > sysfs settings change, rebalance_domains() can get triggered with null > domain on other cpus, which is

Re: [patch] sched: skip updating rq's next_balance under null SD

* Siddha, Suresh B [EMAIL PROTECTED] wrote: Was playing with sched_smt_power_savings/sched_mc_power_savings and found out that while the scheduler domains are reconstructed when sysfs settings change, rebalance_domains() can get triggered with null domain on other cpus, which is setting

[patch] sched: skip updating rq's next_balance under null SD

Was playing with sched_smt_power_savings/sched_mc_power_savings and found out that while the scheduler domains are reconstructed when sysfs settings change, rebalance_domains() can get triggered with null domain on other cpus, which is setting next_balance to jiffies + 60*HZ. Resulting in no

[patch] sched: skip updating rq's next_balance under null SD

Was playing with sched_smt_power_savings/sched_mc_power_savings and found out that while the scheduler domains are reconstructed when sysfs settings change, rebalance_domains() can get triggered with null domain on other cpus, which is setting next_balance to jiffies + 60*HZ. Resulting in no