similar to: [Xen-tools] What''s the main difference between BVT and EDF?,

I''m working on a new hypercall, do_confer, which allows the directed yielding of a vcpu to another vcpu. It is mainly used when a vcpu fails to acquire a spinlock, yielding to the lock holder instead of spinning. I ported the ppc64 spinlock implementation for the i386 linux portion. In implementing the hypercall, I''ve been trying to figure out how to get the scheduler

Are there any examples of bvt scheduler parameters usage? If I understand it right, bvt provides me with option to scale domain''s CPU usage. Eg. I have 2 (non-zero) domains pinned to the same CPU. Can I assign eg. 30% of CPU time to domain 1 and 70% to domain 2? (I mean in peaks when both domains are not idle and require the CPU time) If yes, how should I build the "xm bvt"

This patch -Displays[1] current parameters for running domains ala xm list -Allow users to set[2] one or more parameters[3] without having to provide values for parameters they do not wish to change -Adds additional testing of sched-sedf via new xm-test testcases. With this patch applied, test 02_sedf_period_lower_neg.py exposes a bug[4]. I''ll follow up this email with a patch for

Hello I''m in trouble using the bvt scheduler with the command line. the command "xm sched-bvt help" explain that it need 6 argument but that''s all. I have read a previous conversation for bvt example with command line, but it doesn''t work I try (5 is the id of the concerned

Hi All , I am using older xen version xen-3.0.2 which supports BVT and SEDF scheduler I want to add credit and boost credit scheduler support in xen-3.0.2 . Please let me know if any (Credit scheduler) patch is available for xen-3.0.2 Thanks, Akhilesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I've got the following edf: *** x = c(1.6,1.8,2.4,2.7,2.9,3.3,3.4,3.4,4,5.2) F2.5 <- ecdf(x) plot(F2.5, verticals= TRUE, do.p = TRUE, lwd=3, ylab = "", xlab = "", xlim = c(1,5.5)) abline(h= (0:5)*0.2) #mean abline(v=mean(x), lwd=2) mtext(text=expression(bar(x) == 3.07), side=1, adj=0.462, padj=3, cex=1) *** Now I would like to

Hi everyone, I understand BVT is not the default scheduler anymore, but perhaps this would be of interest to some people. Some changes in the current BVT scheduler compared to the BVT code in Xen 3.0 has affected its correctness. In the original (Xen 3.0) BVT scheduler the weights resulted in correct CPU allocations. However, the current BVT scheduler (CS 10647:8e55c5c11475) does not do it

hi all, im am trying to allocate cpu to the various domains using a bvt scheduler. so now lets say i want to give the first virtual machine a weight of 1 and the second a weight of 2. this should result in domain1 using 33% of the cpu and domain2 66%. however since xm sched-bvt takes inverse of the weights as input so i do 1/1 and 1/2 and hence do "xm sched-bvt vm1 2 0 0 0 0" for the

Hi all, Here are some benchmarks that I''ve done using Xen. However, before I get started, let me explain some of configuration details... Xen Version SPECjbb WebBench Linux Distribution Debian 3.1 HT disabled Linux Kernel 2.6.12.2 Host Patch CK3s Here are the initial benchmarks SPECJBB WebBench 1 Thread 1 Client 2 Clients 4 Clients 8 Clients BOPS TPS TPS TPS TPS Host

I am seeing a problem with Dom0 crashing on x86_64 whenever I create a DomU. I''ve done some more testing, and it appears that this problem is somehow related to networking. Dom0 crashes as soon as the networking services are started when DomU is coming up. As an experiment, I brought up DomU without networking, and it stayed up. As soon as I started DomU with networking enabled, however,

Hi! I''m currently working on Earliest Deadline First qdisc implementation for providing delay bounded real-time services according IntServ architecture under Linux. My first step was simple EDF implementation, that is available from http://www.avalon.ru/~dketov/. If someone interesting in using EDF or just trying and testing it, please go ahead :) Any questions are welcome. Dimitry.

Hi, I have a naive question with the xen BVT scheduler. Supposing I have only one guest domain runnning on domain 0 and with the xm bvt command I have allocated cpu units in the ratio 9:1 to domain 0 and domain 1(say) respectively. Now I create another guest domain. How much CPU share it (or subsequent domains created after it) will get? ~$ubh _______________________________________________

Dear all, First, let's create some data to play around: set.seed(1) (df <- data.frame(Group=rep(c("Group1","Group2","Group3"), each=10), Value=c(rexp(10, 1), rexp(10, 4), rexp(10, 10)))[sample(1:30,30),]) ## Now we need the empirical distribution function: edf <- function(x) ecdf(x)(x) # empirical distribution function evaluated at x ##

We are using GAM in mgcv (Wood), relatively new users, and wonder if anyone can advise us on a problem we are encountering as we analyze many short time series datasets. For each dataset, we have four models, each with intercept, predictor x (trend), z (treatment), and int (interaction between x and z). Our models are Model 1: gama1.1 <- gam(y~x+z+int, family=quasipoisson) ##no smooths Model

9d1fd58ff602 was bogous in not letting a new domain being created if its scheduling parameters --when running under the sedf scheduler-- were not fully specified, making creation fail like in this example here below: 2012-06-16 07:37:47 Z executing ssh ... root@10.80.248.105 xl create /etc/xen/debian.guest.osstest.cfg libxl: error: libxl.c:3619:sched_sedf_domain_set: setting domain sched sedf:

Dear useRs, I reran an analysis with bam (mgcv, version 1.7-17) originally conducted using an older version of bam (mgcv, version 1.7-11) and this resulted in the same estimates, but much lower standard errors (in some cases 20 times as low) and lower p-values. This obviously results in a larger set of significant predictors. Is this result expected given the improvements in the new version? Or

Dear all I have found that the two "equivalent" commands do not produce the same results. 1. (I wrote this command by hand, this is what I would do usually) >summary(aov(eduyrs ~ cntry * edf, data=ESS1)) Df Sum Sq Mean Sq F value Pr(>F) cntry 1 257 256.65 21.2251 4.243e-06 *** edf 4 11010 2752.42 227.6296 <

Currently with the credit scheduler, cpu_weight cannot be assigned to guest domains at boot time.(it can be set with xm sched-weight after booting) This patch allows CPU weight, and CAP to be set by the Xen configuration files. Specification: The following can be added to the Xen configuration files. 1.CPU WEIGHT [OPTIONAL] cpu_weight = cpu weight value -sets the cpu time ratio to be

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU