From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [PATCH 0/7] get rid of the SEDF scheduler
Date: Fri, 26 Jun 2015 18:18:37 +0200 [thread overview]
Message-ID: <20150626161417.29181.992.stgit@Solace.station> (raw)
Hi everyone,
This series is the follow up of this proposal and conversation:
http://lists.xen.org/archives/html/xen-devel/2015-05/msg02874.html
Let me quote this (again), from 2006:
git show db51cd09d37ea44b126bb259f9392248afd768e6
...
diff --git a/docs/src/interface.tex b/docs/src/interface.tex
index c9017c7..9a59840 100644
--- a/docs/src/interface.tex
+++ b/docs/src/interface.tex
@@ -209,8 +209,8 @@ implement timeout values when they block.
Xen offers a uniform API for CPU schedulers. It is possible to choose
from a number of schedulers at boot and it should be easy to add more.
-The SEDF, BVT, and Credit schedulers are part of the normal Xen
-distribution. BVT and SEDF will be going away and their use should be
+The SEDF and Credit schedulers are part of the normal Xen
+distribution. SEDF will be going away and its use should be
avoided once the credit scheduler has stabilized and become the default.
The Credit scheduler provides proportional fair shares of the
host's CPUs to the running domains. It does this while transparently
So, after being "going away" for 9 years, here we are, getting rid of it!
Hopefully, I've killed every sign of it, and did not overlook anything.
I'm not sure whether the python bindings are an interface that we consider
stable. I've killed everything about SEDF from there, but I don't know sure how
to test this. If I should do it differently, let me know.
In libxl, I left the symbols and the data types in place, for the sake of
build-time backward compatibility, but any attempt of calling one of the
scheduler API function with LIBXL_SCHEDULED_SEDF as the scheduler id, results
in an error.
As far as testing goes, I have verified that:
- the repo builds, both xen and tools, at each stage of the series
- booting with sched=sedf no longer works
- with all the series applied, `xl sched-sedf' no longer exists
- with the libxl+libxc patches patch applied (so, with SEDF still available in Xen
and xl), `xl sched-sedf' exists, but produces an error
There is an OSSTest patch that shuts down SEDF testing for xen-unstable
(actually, for everything greater than xen-4.5) here:
http://lists.xen.org/archives/html/xen-devel/2015-06/msg04399.html
Regards,
Dario
---
Dario Faggioli (7):
libxl: get rid of the SEDF scheduler
tools: python: get rid of the SEDF scheduler bindings
libxc: get rid of the SEDF scheduler
xen: get rid of the SEDF scheduler
xen: kill sched_sedf.c
xl: get rid of the SEDF scheduler
docs: get rid of the SEDF scheduler
docs/INDEX | 1
docs/man/xl.cfg.pod.5 | 24
docs/man/xl.pod.1 | 42 -
docs/man/xlcpupool.cfg.pod.5 | 4
docs/misc/sedf_scheduler_mini-HOWTO.txt | 44 -
docs/misc/xen-command-line.markdown | 2
tools/examples/cpupool | 2
tools/libxc/Makefile | 1
tools/libxc/include/xenctrl.h | 12
tools/libxc/xc_sedf.c | 78 --
tools/libxl/libxl.c | 73 -
tools/libxl/libxl_create.c | 61 -
tools/libxl/xl.h | 1
tools/libxl/xl_cmdimpl.c | 139 ---
tools/libxl/xl_cmdtable.c | 16
tools/python/xen/lowlevel/xc/xc.c | 70 -
xen/common/Makefile | 1
xen/common/sched_sedf.c | 1556 -------------------------------
xen/common/schedule.c | 1
xen/include/public/domctl.h | 8
xen/include/public/trace.h | 1
xen/include/xen/sched-if.h | 1
22 files changed, 7 insertions(+), 2131 deletions(-)
delete mode 100644 docs/misc/sedf_scheduler_mini-HOWTO.txt
delete mode 100644 tools/libxc/xc_sedf.c
delete mode 100644 xen/common/sched_sedf.c
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
next reply other threads:[~2015-06-26 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 16:18 Dario Faggioli [this message]
2015-06-26 16:18 ` [PATCH 1/7] libxl: get rid of the SEDF scheduler Dario Faggioli
2015-06-26 16:18 ` [PATCH 2/7] tools: python: get rid of the SEDF scheduler bindings Dario Faggioli
2015-06-26 16:19 ` [PATCH 3/7] libxc: get rid of the SEDF scheduler Dario Faggioli
2015-06-26 16:19 ` [PATCH 4/7] xen: " Dario Faggioli
2015-06-29 11:56 ` Andrew Cooper
2015-06-29 13:29 ` Dario Faggioli
2015-06-26 16:19 ` [PATCH 5/7] xen: kill sched_sedf.c Dario Faggioli
2015-06-26 16:19 ` [PATCH 6/7] xl: get rid of the SEDF scheduler Dario Faggioli
2015-06-26 16:19 ` [PATCH 7/7] docs: " Dario Faggioli
2015-07-02 15:56 ` [PATCH 0/7] " George Dunlap
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=20150626161417.29181.992.stgit@Solace.station \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.