Rename xm commands and cleanup of the "bogus" argument code.

For the "bogus" argument code, avoid changing the argument list so
that errors can be reported consistently.
Signed-off-by: Dan Smith <danms@us.ibm.com>
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
This commit is contained in:
cl349@firebug.cl.cam.ac.uk committed 2005-09-14 17:06:25 +00:00
1 parent ae4ef259f1
commit ca899c5e1e
2 files changed
+64 -59

No files matched your search

+12 -12
View File
@@ -10,7 +10,7 @@ Overview:
Usage:
   -add "sched=sedf" on Xen's boot command-line
   -create domains as usual
   -use "xm sedf <dom-id> <period> <slice> <latency-hint> <extra> <weight>"
   -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
@@ -22,23 +22,23 @@ Usage:
Examples:
 normal EDF (20ms/5ms):
  xm sedf <dom-id> 20000000 5000000 0 0 0
  xm sched-sedf <dom-id> 20000000 5000000 0 0 0
 best-effort domains (i.e. non-realtime):
  xm sedf <dom-id> 20000000 0 0 1 0
  xm sched-sedf <dom-id> 20000000 0 0 1 0
 
normal EDF (20ms/5ms) + share of extra-time:
  xm 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 sedf <d1> 0 0 0 0 2
  xm sedf <d2> 0 0 0 0 3
  xm sedf <d3> 0 0 0 0 4
  xm sedf <d4> 0 0 0 0 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 sedf <d1> 10000000 3000000 0 0 0
  xm sedf <d2> 0 0 0 0 2
  xm sedf <d3> 0 0 0 0 7
  xm sedf <d4> 0 0 0 0 3
  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
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.