linux-kernel - Re: Thread Scheduler

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:	Sun, 23 Mar 2014 04:01:18 -0700 (PDT)
From:	Mahmood Naderan <nt_mahmood@...oo.com>
To:	Mike Galbraith <umgwanakikbuti@...il.com>
Cc:	Jack Carrozzo <jack@...pinc.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Thread Scheduler

>On Thursday, March 20, 2014 6:53 AM, Mike Galbraith <umgwanakikbuti@...il.com> wrote:
>
>marge:~ # man -k setscheduler getscheduler
>sched_setscheduler (2) - set and get scheduling policy/parameters
>sched_setscheduler (3p) - set scheduling policy and parameters (REALTIME)
>sched_getscheduler (2) - set and get scheduling policy/parameters
>sched_getscheduler (3p) - get scheduling policy (REALTIME)

OK I read them and it seems that in order to change the scheduler, I have to write a C code and call the sched_set* functions. Please correct that if I am wrong.

So in order to use my custom scheduler, I have to do the following steps.

1- Write my  code using the APIs and save that in kernel/sched_custom.c
2- Invoke sched_custom.c in kernel/sched.c
3- Recompile the kernel source
4- Reboot using the new kernel
5- write a C code and call sched_setschedule() to use my scheduler.

Is that all? Your reply is appreciated.

Regards,
Mahmood 
--
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/