linux-kernel - Re: [PATCH v2] sched: add a tuning knob to allow changing RR tmeslice

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: <20130124165955.GA9324@gmail.com>
Date:	Thu, 24 Jan 2013 17:59:55 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Clark Williams <williams@...hat.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH v2] sched: add a tuning knob to allow changing RR tmeslice


* Clark Williams <williams@...hat.com> wrote:

> This version stores the user-input value in a separate 
> location from the jiffies values used by the scheduler, to 
> prevent a race condition.
> 
> Subject: [PATCH v2] sched: add a tuning knob to allow changing 
> RR timeslice

looks useful.

> @@ -2010,7 +2010,7 @@ static void task_tick_rt(struct rq *rq, struct
> task_struct *p, int queued) if (--p->rt.time_slice)
>  		return;
>  
> -	p->rt.time_slice = RR_TIMESLICE;
> +	p->rt.time_slice = sched_rr_timeslice;
>  
>  	/*
>  	 * Requeue to the end of queue if we (and all of our
> ancestors) are the @@ -2041,7 +2041,7 @@ static unsigned int
> get_rr_interval_rt(struct rq *rq, struct task_struct *task)
>  	 * Time slice is 0 for SCHED_FIFO tasks

Patch wont apply due to patch corruption, alas.

Thanks,

	Ingo
--
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/