Linux on 390 Port <LINUX-390@VM.MARIST.EDU> wrote on 10/23/2013 10:46:35 AM:
> From: Richard Troth <ri...@velocitysoftware.com> > To: LINUX-390@VM.MARIST.EDU, > Date: 10/23/2013 10:46 AM > Subject: Re: Seeing a lot of "scale_rt_power" messages > Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> > > I haven't seen it that I recall, but a Google search suggests that it > comes from load balancing when you're "running tickless". > > > scale_rt_power: clock:3806a691fbdb1 age:3806a4e60fe00, avg:5d4b8d2f > > The scheduler is trying to tell you something (because the > scale_rt_power() function is in the scheduler), but the context is > lost. > > Does this guest have multiple CPUs? 2 cpu's defined. We have other guests with multiple CPU's but don't exhibit this behavior. > Also, have you made any tuning changes over its life? (Things handled > by 'sysctl' or /etc/sysctl.conf.) Not that I am aware of. > What is the output of ... > > sysctl -a | grep sched kernel.sched_child_runs_first = 0 kernel.sched_min_granularity_ns = 4000000 kernel.sched_latency_ns = 12000000 kernel.sched_wakeup_granularity_ns = 5000000 kernel.sched_tunable_scaling = 1 kernel.sched_migration_cost = 500000 kernel.sched_nr_migrate = 32 kernel.sched_time_avg = 1000 kernel.sched_shares_window = 10000000 kernel.sched_rt_period_us = 1000000 kernel.sched_rt_runtime_us = 950000 kernel.sched_compat_yield = 0 kernel.sched_cfs_bandwidth_slice_us = 5000 kernel.sched_domain.cpu0.domain0.min_interval = 1 kernel.sched_domain.cpu0.domain0.max_interval = 4 kernel.sched_domain.cpu0.domain0.busy_idx = 2 kernel.sched_domain.cpu0.domain0.idle_idx = 1 kernel.sched_domain.cpu0.domain0.newidle_idx = 0 kernel.sched_domain.cpu0.domain0.wake_idx = 0 kernel.sched_domain.cpu0.domain0.forkexec_idx = 0 kernel.sched_domain.cpu0.domain0.busy_factor = 64 kernel.sched_domain.cpu0.domain0.imbalance_pct = 125 kernel.sched_domain.cpu0.domain0.cache_nice_tries = 1 kernel.sched_domain.cpu0.domain0.flags = 4143 kernel.sched_domain.cpu0.domain0.name = CPU kernel.sched_domain.cpu1.domain0.min_interval = 1 kernel.sched_domain.cpu1.domain0.max_interval = 4 kernel.sched_domain.cpu1.domain0.busy_idx = 2 kernel.sched_domain.cpu1.domain0.idle_idx = 1 kernel.sched_domain.cpu1.domain0.newidle_idx = 0 kernel.sched_domain.cpu1.domain0.wake_idx = 0 kernel.sched_domain.cpu1.domain0.forkexec_idx = 0 kernel.sched_domain.cpu1.domain0.busy_factor = 64 kernel.sched_domain.cpu1.domain0.imbalance_pct = 125 kernel.sched_domain.cpu1.domain0.cache_nice_tries = 1 kernel.sched_domain.cpu1.domain0.flags = 4143 kernel.sched_domain.cpu1.domain0.name = CPU > > Also, what do your boot parms look like? (Look for HZ timer and other > scheduler tweaks.) No parms on the boot for scheduler or HZ timer. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
