From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Brandon Philips <brandon@ifup.org>
Cc: mingo@elte.hu, rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Export CPU Scheduler Tunables via DebugFS
Date: Sun, 3 Sep 2006 19:12:02 +0200 [thread overview]
Message-ID: <20060903171202.GA1290@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060903132802.GD10120@plankton.ifup.org>
Hi,
On Sun, Sep 03, 2006 at 08:28:02AM -0500, Brandon Philips wrote:
> This patch exports the CPU scheduler tunables via DebugFS.
> +int min_timeslice;
> +#define MIN_TIMESLICE (min_timeslice)
> +int def_timeslice;
> +#define DEF_TIMESLICE (def_timeslice)
> +int on_runqueue_weight;
> +#define ON_RUNQUEUE_WEIGHT (on_runqueue_weight)
> +int child_penalty;
> +#define CHILD_PENALTY (child_penalty)
> +int parent_penalty;
> +#define PARENT_PENALTY (parent_penalty)
> +int exit_weight;
> +#define EXIT_WEIGHT (exit_weight)
> +int prio_bonus_ratio;
> +#define PRIO_BONUS_RATIO (prio_bonus_ratio)
> +int max_bonus;
> +#define MAX_BONUS (max_bonus)
> +int interactive_delta;
> +#define INTERACTIVE_DELTA (interactive_delta)
> +int max_sleep_avg;
> +#define MAX_SLEEP_AVG (max_sleep_avg)
> +int starvation_limit;
> +#define STARVATION_LIMIT (starvation_limit)
__read_mostly? Except for those variables which are being tweaked
quite often by live scheduler code... (probably none)
This only concerns the case of CONFIG_DEBUGFS_SCHED being activated,
but it may still be nice to have, I think, since scheduler stuff
should rather be fast than slow.
But since it is a debugging-only option omitting __read_mostly may
make sense...
Andreas Mohr
--
VGER BF report: H 0.00129204
prev parent reply other threads:[~2006-09-03 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 13:28 [PATCH] Export CPU Scheduler Tunables via DebugFS Brandon Philips
2006-09-03 17:12 ` Andreas Mohr [this message]
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=20060903171202.GA1290@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=brandon@ifup.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
/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