linux-kernel - Re: changing timeslice in linux

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]

Date:	Mon, 20 Aug 2012 07:51:52 -0700
From:	Xin Tong <xerox.time.tech@...il.com>
To:	Mike Galbraith <efault@....de>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: changing timeslice in linux

On Sun, Aug 19, 2012 at 10:54 PM, Mike Galbraith <efault@....de> wrote:
> On Sun, 2012-08-19 at 11:58 -0700, Xin Tong wrote:
>> I have 2 questions about linux 2.6 x86_64 scheduler.
>>
>> 1. is the default scheduling algorithm SCHED_NORMAL in linux ?
>
> Yes.
Is there any document describing what the sched_normal is ? it is more
difficult than SCHED_RR to infer its meaning just based on its name ?
>
>> 2. how do i change the time slice in linux source code ?
>
> You shouldn't need to.  You can tune "slice" by adjusting
> sched_latency_ns and sched_min_granularity_ns, but note that "slice" is
> not a fixed quantum.  Also note that CFS preemption decisions are based
> upon instantaneous state.  A task may have received a full (variable)
> "slice" of CPU time, but preemption will be triggered only if a more
> deserving task is available, so a "slice" is not the "max uninterrupted
> CPU time" that you may expect it to be.. but it is somewhat similar.
>
> -Mike
>
This can be done without recompiling and reinstalling the kernel ?
maybe one simply needs to write to a device file under /dev ?

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