linux-kernel - Re: [GIT RFC PULL rcu/urgent] Prevent Kconfig from asking pointless questions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150420143440.49e1e537@gandalf.local.home>
Date:	Mon, 20 Apr 2015 14:34:40 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Clark Williams <williams@...hat.com>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	a.p.zijlstra@...llo.nl, akpm@...ux-foundation.org,
	linux-rt-users@...r.kernel.org
Subject: Re: [GIT RFC PULL rcu/urgent] Prevent Kconfig from asking pointless
 questions

On Mon, 20 Apr 2015 20:28:32 +0200
Ingo Molnar <mingo@...nel.org> wrote:

> Instrumentation - especially instrumentation that should have been 
> implemented mostly in user-space, like ftrace ;-) - is another special 
> case that should stay as flexible as possible via sysctls, obviously.

I know I used ftrace as an example, but a more appropriate example
would be the sched knobs, as this is more about rcu scheduling than
anything else.

See:

sched_autogroup_enabled      sched_rr_timeslice_ms
sched_child_runs_first       sched_rt_period_us
sched_domain/                sched_rt_runtime_us
sched_latency_ns             sched_shares_window_ns
sched_migration_cost_ns      sched_time_avg_ms
sched_min_granularity_ns     sched_tunable_scaling
sched_nr_migrate             sched_wakeup_granularity_ns

In particular, the sched_rt_* ones.


-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/