[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH 10 of 17] docs: remove non-breaking spaces from sedf_scheduler_mini-HOWTO.txt
# HG changeset patch # User Ian Campbell <ian.campbell@xxxxxxxxxx> # Date 1321541652 0 # Node ID 617f5d6e9e69b4f6362df91f078b7dc2abdbd80a # Parent c4571d33f5829bac2e1da169f9d1398810c0b7d2 docs: remove non-breaking spaces from sedf_scheduler_mini-HOWTO.txt This document contains several 0xa0 characters (non-breaking spaces). These do not display correctly in (some) terminals or when the document is rendered by (some) browsers. Re-encode them as spaces. I'm not confident that this change will make it through being encoded as a patch and sent through email. Its effect can be replicated with: perl -i -p -e 's/\xa0/ /g' docs/misc/sedf_scheduler_mini-HOWTO.txt Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> diff -r c4571d33f582 -r 617f5d6e9e69 docs/misc/sedf_scheduler_mini-HOWTO.txt --- a/docs/misc/sedf_scheduler_mini-HOWTO.txt Thu Nov 17 14:35:37 2011 +0000 +++ b/docs/misc/sedf_scheduler_mini-HOWTO.txt Thu Nov 17 14:54:12 2011 +0000 @@ -8,37 +8,37 @@ Overview: uses realtime-algorithms to ensure time guarantees. Usage: - -add "sched=sedf" on Xen's boot command-line - -create domains as usual - -use "xm sched-sedf <dom-id> <period> <slice> <latency-hint> <extra> <weight>" - Where: - -period/slice are the normal EDF scheduling parameters in nanosecs - -latency-hint is the scaled period in case the domain is doing heavy I/O + -add "sched=sedf" on Xen's boot command-line + -create domains as usual + -use "xm sched-sedf <dom-id> <period> <slice> <latency-hint> <extra> <weight>" + Where: + -period/slice are the normal EDF scheduling parameters in nanosecs + -latency-hint is the scaled period in case the domain is doing heavy I/O (unused by the currently compiled version) - -extra is a flag (0/1), which controls whether the domain can run in + -extra is a flag (0/1), which controls whether the domain can run in extra-time - -weight is mutually exclusive with period/slice and specifies another + -weight is mutually exclusive with period/slice and specifies another way of setting a domains cpu slice Examples: - normal EDF (20ms/5ms): - xm sched-sedf <dom-id> 20000000 5000000 0 0 0 + normal EDF (20ms/5ms): + xm sched-sedf <dom-id> 20000000 5000000 0 0 0 - best-effort domains (i.e. non-realtime): - xm sched-sedf <dom-id> 20000000 0 0 1 0 - + best-effort domains (i.e. non-realtime): + xm sched-sedf <dom-id> 20000000 0 0 1 0 + normal EDF (20ms/5ms) + share of extra-time: - xm sched-sedf <dom-id> 20000000 5000000 0 1 0 + xm sched-sedf <dom-id> 20000000 5000000 0 1 0 - 4 domains with weights 2:3:4:2 - xm sched-sedf <d1> 0 0 0 0 2 - xm sched-sedf <d2> 0 0 0 0 3 - xm sched-sedf <d3> 0 0 0 0 4 - xm sched-sedf <d4> 0 0 0 0 2 + 4 domains with weights 2:3:4:2 + xm sched-sedf <d1> 0 0 0 0 2 + xm sched-sedf <d2> 0 0 0 0 3 + xm sched-sedf <d3> 0 0 0 0 4 + xm sched-sedf <d4> 0 0 0 0 2 - 1 fully-specified (10ms/3ms) domain, 3 other domains share - available rest in 2:7:3 ratio: - xm sched-sedf <d1> 10000000 3000000 0 0 0 - xm sched-sedf <d2> 0 0 0 0 2 - xm sched-sedf <d3> 0 0 0 0 7 - xm sched-sedf <d4> 0 0 0 0 3 + 1 fully-specified (10ms/3ms) domain, 3 other domains share + available rest in 2:7:3 ratio: + xm sched-sedf <d1> 10000000 3000000 0 0 0 + xm sched-sedf <d2> 0 0 0 0 2 + xm sched-sedf <d3> 0 0 0 0 7 + xm sched-sedf <d4> 0 0 0 0 3 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |