From: Henrik Austad <henrik@austad.us>
To: Ran Shalit <ranshalit@gmail.com>
Cc: Alison Chaiken <alison@peloton-tech.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: EDF - "earliest deadline first" scheduler
Date: Tue, 4 Apr 2017 07:42:47 +0200 [thread overview]
Message-ID: <20170404054247.GE12288@icarus.home.austad.us> (raw)
In-Reply-To: <CAJ2oMhKPbh5BJW+JBGtLSvUxukB2e1MA_DierJ1P6k5Cbs+Ohg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
On Mon, Apr 03, 2017 at 08:06:23AM +0300, Ran Shalit wrote:
> On Mon, Apr 3, 2017 at 5:38 AM, Alison Chaiken <alison@peloton-tech.com> wrote:
> > Ran Shalit <ranshalit@gmail.com> wrote:
> >> I have found in
> >> https://wiki.linuxfoundation.org/realtime/documentation/howto/applications/cyclic
> >> that there is EDF scheduler option for creating a periodic RT thread.
> >> Yet, I could not understand what's behind the EDF scheduler
> >
> >
> > Have a look at "Using SCHED_DEADLINE" at
> >
> > http://elinux.org/ELC_Europe_2016_Presentations
> >
> > Also, look for papers on this topic by Juri Lelli.
> >
> > HTH,
> > Alison
>
> Hi Alison,
>
> Thank you very much.
> I reviewed the material, which is very interesting, but I am not yet
> sure which timer are used internally in SCHED_DEADLINE.
> Is it posix or non-posix ?
A "posix-timer" is a userspace-construct. A posix-timer will use the
hrtimer in the kernel - which ends up in the same subsystem used by the
deadline scheduler.
--
Henrik Austad
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-04-04 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 2:38 EDF - "earliest deadline first" scheduler Alison Chaiken
2017-04-03 5:06 ` Ran Shalit
2017-04-04 5:42 ` Henrik Austad [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-03 12:53 Ran Shalit
2017-04-04 5:38 ` Henrik Austad
2017-04-04 7:30 ` Ran Shalit
2017-04-02 14:27 Ran Shalit
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=20170404054247.GE12288@icarus.home.austad.us \
--to=henrik@austad.us \
--cc=alison@peloton-tech.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=ranshalit@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;
as well as URLs for NNTP newsgroup(s).