Re: [PATCH] specific do_timer_cpu value for nohz off mode

[Thomas Gleixner]

On Tue, 23 Aug 2011, Dimitri Sivanich wrote:
> On Wed, Aug 17, 2011 at 06:47:43PM +0200, Thomas Gleixner wrote:
> > On Wed, 17 Aug 2011, Dimitri Sivanich wrote:
> While not necessarily harmful, doing jiffies updates on an application cpu
> does cause some extra overhead that HPC benchmarking people notice.  They
> prefer to have OS activity isolated to certain cpus.  They like reproducibility
> of results, and having jiffies updates bouncing around introduces variability.
> 
> Maybe this is useful for other folks as well?  It does give an indication
> of which cpu is currently doing jiffies updates.
> 
> The patch below puts the file in /proc/sys/kernel, but if you think it should be in
> /sys, please let me know where you'd like to see it.

/sys/devices/system/timekeeping/timekeeping0/....
 
Please

> 
> Signed-off-by: Dimitri Sivanich <sivanich@xxxxxxx>
> ---
>  include/linux/tick.h        |    5 +++++
>  kernel/sysctl.c             |    9 +++++++++
>  kernel/time/tick-internal.h |    1 -
>  kernel/time/tick-sched.c    |   23 +++++++++++++++++++++++
>  4 files changed, 37 insertions(+), 1 deletion(-)
> 
> Index: linux/kernel/sysctl.c
> ===================================================================
> --- linux.orig/kernel/sysctl.c
> +++ linux/kernel/sysctl.c
> @@ -57,6 +57,7 @@
>  #include <linux/pipe_fs_i.h>
>  #include <linux/oom.h>
>  #include <linux/kmod.h>
> +#include <linux/tick.h>
>  
>  #include <asm/uaccess.h>
>  #include <asm/processor.h>
> @@ -368,6 +369,14 @@ static struct ctl_table kern_table[] = {
>  		.mode		= 0644,
>  		.proc_handler	= sched_rt_handler,
>  	},
> +	{
> +		.procname	= "sched_jiffies_cpu",
> +		.data		= &tick_do_timer_cpu,
> +		.maxlen		= sizeof(int),
> +		.mode		= 0644,
> +		.proc_handler	= tick_do_timer_cpu_handler,
> +		.extra1		= &zero,
> +	},
>  #ifdef CONFIG_SCHED_AUTOGROUP
>  	{
>  		.procname	= "sched_autogroup_enabled",
> Index: linux/include/linux/tick.h
> ===================================================================
> --- linux.orig/include/linux/tick.h
> +++ linux/include/linux/tick.h
> @@ -72,6 +72,11 @@ struct tick_sched {
>  extern void __init tick_init(void);
>  extern int tick_is_oneshot_available(void);
>  extern struct tick_device *tick_get_device(int cpu);
> +extern int tick_do_timer_cpu_handler(struct ctl_table *table, int write,
> +				 void __user *buffer, size_t *lenp,
> +				 loff_t *ppos);
> +
> +extern int tick_do_timer_cpu __read_mostly;
>  
>  # ifdef CONFIG_HIGH_RES_TIMERS
>  extern int tick_init_highres(void);
> Index: linux/kernel/time/tick-sched.c
> ===================================================================
> --- linux.orig/kernel/time/tick-sched.c
> +++ linux/kernel/time/tick-sched.c
> @@ -815,6 +815,29 @@ void tick_cancel_sched_timer(int cpu)
>  }
>  #endif
>  
> +int tick_do_timer_cpu_handler(struct ctl_table *table, int write,
> +		void __user *buffer, size_t *lenp, loff_t *ppos)
> +{
> +	int ret, old_val;
> +
> +#ifdef CONFIG_NO_HZ
> +	/* nohz mode not supported */
> +	if (write && tick_nohz_enabled)
> +		return -EINVAL;
> +#endif
> +
> +	old_val = tick_do_timer_cpu;
> +
> +	ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> +
> +	if (!ret && write && !cpu_online(tick_do_timer_cpu)) {
> +		tick_do_timer_cpu = old_val;
> +		return -EINVAL;
> +	}
> +
> +	return ret;
> +}
> +
>  /**
>   * Async notification about clocksource changes
>   */
> Index: linux/kernel/time/tick-internal.h
> ===================================================================
> --- linux.orig/kernel/time/tick-internal.h
> +++ linux/kernel/time/tick-internal.h
> @@ -12,7 +12,6 @@
>  DECLARE_PER_CPU(struct tick_device, tick_cpu_device);
>  extern ktime_t tick_next_period;
>  extern ktime_t tick_period;
> -extern int tick_do_timer_cpu __read_mostly;
>  
>  extern void tick_setup_periodic(struct clock_event_device *dev, int broadcast);
>  extern void tick_handle_periodic(struct clock_event_device *dev);
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/