From: Frederic Weisbecker <fweisbec@gmail.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: linaro-kernel@lists.linaro.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Clark Williams <clark.williams@gmail.com>,
Tony Luck <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>, Mel Gorman <mgorman@suse.de>,
Rik van Riel <riel@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] sched/nohz: add sysctl control over sched_tick_max_deferment
Date: Wed, 19 Jun 2013 20:42:40 +0200 [thread overview]
Message-ID: <20130619184238.GD21522@somewhere.redhat.com> (raw)
In-Reply-To: <1371599913-1232-1-git-send-email-khilman@linaro.org>
On Tue, Jun 18, 2013 at 04:58:28PM -0700, Kevin Hilman wrote:
> Allow sysctl override of sched_tick_max_deferment in order to ease
> finding/fixing the remaining issues with full nohz.
>
> The value to be written is in jiffies, and -1 means the max deferment
> is disabled (scheduler_tick_max_deferment() returns KTIME_MAX.)
>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Signed-off-by: Kevin Hilman <khilman@linaro.org>
This looks like a useful thing but I wonder if a debugfs file would
be more appropriate than sysctl.
The scheduler tick max deferment is supposed to be a temporary
hack so we probably don't want to bring a real user ABI for that.
I believe sysctl is for permanent ABIs, right?
next prev parent reply other threads:[~2013-06-19 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 23:58 [PATCH 1/2] sched/nohz: add sysctl control over sched_tick_max_deferment Kevin Hilman
2013-06-18 23:58 ` [PATCH 2/2] sched/nohz: fix overflow error in scheduler_tick_max_deferment() Kevin Hilman
2013-06-19 19:06 ` Frederic Weisbecker
2013-06-19 18:42 ` Frederic Weisbecker [this message]
2013-06-19 20:34 ` [PATCH 1/2] sched/nohz: add sysctl control over sched_tick_max_deferment Kevin Hilman
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=20130619184238.GD21522@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clark.williams@gmail.com \
--cc=keescook@chromium.org \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.