From: Andreas Mohr <andi@lisas.de>
To: Mahmood Naderan <nt_mahmood@yahoo.com>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
Jack Carrozzo <jack@crepinc.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Thread Scheduler
Date: Mon, 24 Mar 2014 21:30:32 +0100 [thread overview]
Message-ID: <20140324203032.GA16964@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <1395572478.74811.YahooMailNeo@web141601.mail.bf1.yahoo.com>
Hi,
> 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.
No, AFAIK these are *user-space* APIs, thus they're supposed to be used by
applications (correct me if I'm wrong).
So the question would be what exactly you're trying to achieve:
either you want to actively modify the kernel-side scheduler sources,
in which case these APIs probably are not what you want (to use there),
or you're trying to modify scheduling configuration of user-space applications,
in which case they possibly are.
Or you want both, in which case you probably
modify kernel scheduler implementation *and* use sched_*() in user-space
with the intent to ensure that that modified scheduler implementation
gets chosen.
HTH,
Andreas Mohr
prev parent reply other threads:[~2014-03-24 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 9:57 Mahmood Naderan
2014-03-19 11:27 ` Mike Galbraith
2014-03-19 11:34 ` Mahmood Naderan
2014-03-19 12:06 ` Jack Carrozzo
2014-03-19 20:01 ` Mahmood Naderan
2014-03-20 2:23 ` Mike Galbraith
2014-03-23 11:01 ` Mahmood Naderan
2014-03-23 14:05 ` Mark Knecht
2014-03-23 14:27 ` Mahmood Naderan
2014-03-23 15:04 ` Mark Knecht
2014-03-24 20:30 ` 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=20140324203032.GA16964@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=jack@crepinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nt_mahmood@yahoo.com \
--cc=umgwanakikbuti@gmail.com \
/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
all inboxes | Powered by JetHome®