public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] specific do_timer_cpu value for nohz off mode
Date: Tue, 22 Nov 2011 16:08:02 -0800	[thread overview]
Message-ID: <20111122160802.e99d6218.akpm@linux-foundation.org> (raw)
In-Reply-To: <20111108191149.GA7236@sgi.com>

On Tue, 8 Nov 2011 13:11:49 -0600
Dimitri Sivanich <sivanich@sgi.com> wrote:

> Resending this.

Not enough times apparently :(
 
> 
> Allow manual override of the tick_do_timer_cpu.
> 
> 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.

This doesn't really explain what the patch does.  "override" with what?
What effects can the user expect to see from doing
the-action-which-you-didn't-describe?

> ===================================================================
> --- linux.orig/kernel/time/tick-sched.c
> +++ linux/kernel/time/tick-sched.c
> @@ -834,6 +834,104 @@ void tick_cancel_sched_timer(int cpu)
>  }
>  #endif
>  
> +
> +#ifdef CONFIG_SYSFS
> +/**
> + * sysfs_show_do_timer_cpu - sysfs interface for tick_do_timer_cpu
> + * @dev:        unused
> + * @buf:        char buffer where value of tick_do_timer_cpu is copied
> + *
> + * Provides sysfs interface for showing the current tick_do_timer_cpu.
> + */
> +static ssize_t
> +sysfs_show_do_timer_cpu(struct sys_device *dev,
> +				struct sysdev_attribute *attr, char *buf)
> +{
> +	ssize_t count = 0;
> +
> +	count = snprintf(buf, PAGE_SIZE, "%d\n", tick_do_timer_cpu);
> +
> +	return count;

Save some trees:

	return snprintf(buf, PAGE_SIZE, "%d\n", tick_do_timer_cpu);

> +}
> +
> +/**
> + * sysfs_override_do_timer_cpu - manually override tick_do_timer_cpu
> + * @dev:        unused
> + * @buf:        cpu number of desired tick_do_timer_cpu
> + * @count:      length of buffer
> + *
> + * Takes input from sysfs interface for manually overriding the selected
> + * tick_do_timer_cpu.  Only applicable when not running in nohz mode.
> + */
> +static ssize_t
> +sysfs_override_do_timer_cpu(struct sys_device *dev,
> +					struct sysdev_attribute *attr,
> +					const char *buf, size_t count)
> +{
> +	char b[16];
> +	size_t ret = count;
> +	int c;
> +
> +#ifdef CONFIG_NO_HZ
> +	/* nohz mode not supported */
> +	if (tick_nohz_enabled)
> +		return -EINVAL;
> +#endif
> +	/* strings from sysfs write are not 0 terminated! */

hm.  Aren't they?

> +	if (count >= sizeof(b))
> +		return -EINVAL;
> +
> +	/* strip off \n: */
> +	if (buf[count-1] == '\n')
> +		count--;
> +	if (count < 1)
> +		return -EINVAL;
> +
> +	memcpy(b, buf, count);
> +	b[count] = 0;
> +
> +	if (sscanf(b, "%d", &c) != 1)
> +		return -EINVAL;

You should be able to use strim() in here, and eliminate b[].  Not that
the \n needed to be removed anyway!  I think it's OK to modify the
incoming memory for sysfs write handlers.

Also, kstrto*() should be used to detect and reject input of the form
"42foo".

But surely we have a helper function somewhere to read an integer out
of a sysfs-written buffer.  If not, we should!

> +	if (!cpu_online(c))
> +		return -EINVAL;
> +
> +	tick_do_timer_cpu = c;
> +
> +	return ret;
> +}
> +
> +/*
> + * Sysfs setup bits:
> + */
> +static SYSDEV_ATTR(jiffies_cpu, 0644, sysfs_show_do_timer_cpu,
> +		   sysfs_override_do_timer_cpu);
> +
> +static struct sysdev_class timekeeping_sysclass = {
> +	.name = "timekeeping",
> +};

The patch shouod add some user-facing documentation for the user-facing
feature.

> +static struct sys_device device_timekeeping = {
> +	.id     = 0,
> +	.cls    = &timekeeping_sysclass,
> +};
> +
> +static int __init init_timekeeping_sysfs(void)
> +{
> +	int error = sysdev_class_register(&timekeeping_sysclass);
> +
> +	if (!error)
> +		error = sysdev_register(&device_timekeeping);
> +	if (!error)
> +		error = sysdev_create_file(
> +				&device_timekeeping,
> +				&attr_jiffies_cpu);
> +	return error;
> +}
> +
> +device_initcall(init_timekeeping_sysfs);
> +#endif /* SYSFS */


  reply	other threads:[~2011-11-23  0:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 19:11 [PATCH] specific do_timer_cpu value for nohz off mode Dimitri Sivanich
2011-11-23  0:08 ` Andrew Morton [this message]
2011-11-30 15:29   ` Dimitri Sivanich
2011-12-01  0:11     ` Andrew Morton
2011-12-01  0:16       ` Andrew Morton
2011-12-01  2:07         ` Dimitri Sivanich
2011-12-01  2:13           ` Andrew Morton
2011-12-01 16:37             ` Dimitri Sivanich
2011-12-01 22:56               ` Andrew Morton
2011-12-02 20:14                 ` Dimitri Sivanich
2011-12-02 20:22                   ` Dimitri Sivanich
2011-12-02 22:42                   ` Thomas Gleixner
2011-12-01  2:06       ` Dimitri Sivanich
2011-12-01  2:12         ` Andrew Morton
2011-12-01  2:34           ` Dimitri Sivanich
2011-12-01  2:38             ` Andrew Morton
2012-01-15 13:46 ` Mike Galbraith
2012-01-15 14:04   ` Mike Galbraith
2012-01-15 14:23   ` Mike Galbraith
2012-01-25 11:27   ` Mike Galbraith
2012-02-15 14:16 ` Thomas Gleixner
2012-02-15 14:37   ` Dimitri Sivanich
2012-02-15 14:52     ` Thomas Gleixner
2012-02-15 15:34       ` Dimitri Sivanich
2012-02-15 20:36         ` Thomas Gleixner
2012-02-16 14:59           ` Dimitri Sivanich
2013-03-19 17:03             ` [PATCH][RFC] " Jiri Bohac
  -- strict thread matches above, loose matches on Subject: below --
2011-08-17 16:07 [PATCH] " Dimitri Sivanich
2011-08-17 16:47 ` Thomas Gleixner
2011-08-23 19:56   ` Dimitri Sivanich
2011-09-02  8:19     ` Thomas Gleixner
2011-09-02 19:29       ` Dimitri Sivanich
2011-09-02 19:57         ` Thomas Gleixner
2011-09-02 20:39           ` Dimitri Sivanich
2011-08-03 19:57 Dimitri Sivanich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111122160802.e99d6218.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sivanich@sgi.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox