From: Juri Lelli <juri.lelli@gmail.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Workshop on Real-Time Scheduling in the Linux Kernel (RTS-LIKE) [was SCHED_DEADLINE hands-on workshop]
Date: Mon, 9 Jun 2014 09:55:03 +0200 [thread overview]
Message-ID: <20140609095503.41a80ead8450dcf868e5f989@gmail.com> (raw)
[Our sincere apologies if you receive multiple copies of this announce]
----------------------------------------------------------------------
Workshop on Real-Time Scheduling in the Linux Kernel (RTS-LIKE)
June 26-27, 2014
Scuola Superiore Sant'Anna
Pisa, Italy
***** Registration deadline June 19, 2014 *****
----------------------------------------------------------------------
Web site: http://retis.sssup.it/rts-like/
----------------------------------------------------------------------
Since March 30 2014, the new scheduling class SCHED_DEADLINE is
available in the Linux kernel (from version 3.14). This opportunity
enables the enforcement of a real-time behavior to the scheduled
threads.
The Workshop on Real-Time Scheduling in the Linux Kernel (RTS-LIKE)
aims at introducing the participants to real-time issues when
scheduling threads, and present how this issues are addressed with the
SCHED_DEADLINE scheduling class.
Finally, the SCHED_DEADLINE internals and the current development
status will be presented, as well as an open discussion on future
directions of the Linux kernel scheduler
----------------------------------------------------------------------
PROGRAM
Thursday 26/06/2014
Morning
- Welcome
- Real-time scheduling and threads: basics (Luca Abeni, Giorgio
Buttazzo)
- SCHED_DEADLINE: presentation, how to use it (Juri Lelli)
- Use cases with time-sensitive characteristics (contributors)
Lunch break
Afternoon
- hands-on session: play with SCHED_DEADLINE: participants will
attach SCHED_DEADLINE to the preferred application
Social event (dinner in Marina di Pisa)
Friday 27/06/2014
Morning
- Overview of the Linux scheduler framework (speaker to be
confirmed)
- SCHED_DEADLINE: internals and current development status (Juri
Lelli)
- Panel on open problems and future development directions in
Linux kernel scheduler
Lunch break
Afternoon
- hands-on session: modify, compile, and debug your own kernel
----------------------------------------------------------------------
MORE INFO
Details about live streaming and workshop recorded sessions will
follow shortly.
----------------------------------------------------------------------
IMPORTANT DATES
Registration deadline: June 19, 2014
Workshop: June 26-27, 2014
----------------------------------------------------------------------
ORGANIZERS
Luca Abeni, University of Trento
Enrico Bini, Scuola Superiore Sant'Anna, Pisa
Juri Lelli, Scuola Superiore Sant'Anna, Pisa
----------------------------------------------------------------------
next reply other threads:[~2014-06-09 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 7:55 Juri Lelli [this message]
2014-06-25 19:08 ` Workshop on Real-Time Scheduling in the Linux Kernel (RTS-LIKE) [was SCHED_DEADLINE hands-on workshop] Juri Lelli
2014-06-25 19:15 ` Pavel Vasilyev
2014-06-26 6:30 ` Christian Gmeiner
2014-06-30 8:16 ` Juri Lelli
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=20140609095503.41a80ead8450dcf868e5f989@gmail.com \
--to=juri.lelli@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
/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).