search for: 20us

Hi Jason, I understand your busy loop timeout is quite conservative at 50us. Did you try any other values? Also, did you measure how polling affects many VMs talking to each other (e.g. 20 VMs on each host, perhaps with several vNICs each, transmitting to a corresponding VM/vNIC pair on another host)? On a complete separate experiment (busy waiting on storage I/O rings on Xen), I have observed

Hi Jason, I understand your busy loop timeout is quite conservative at 50us. Did you try any other values? Also, did you measure how polling affects many VMs talking to each other (e.g. 20 VMs on each host, perhaps with several vNICs each, transmitting to a corresponding VM/vNIC pair on another host)? On a complete separate experiment (busy waiting on storage I/O rings on Xen), I have observed

...the current counter value is too close to the comparator value to be reprogrammed the expected HPET intr may be missing. Linux kernel uses a mininal 48-hpet-ticks(~3.5us) distance to workaround this, but personal observation showed there is still failure case while delta=0xba (~13.5us). So choosing 20us as the MIN_DELTA_NS should be helpful to prevent near-missing from happening. local_irq_save/restore were used to avoid disturbance. (+ 2) was used as a final guard to avoid wrong judgement due to the real happened near-missing case. Signed-off-by: Wei Gang <gang.wei@intel.com> Signed-off-b...

...tances 1063: 109.617: Starting 1 rand-thread threads 1062: 112.627: Running... 1062: 213.627: Run took 100 seconds... 1062: 213.628: Per-Operation Breakdown rand-rate 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu rand-read1 41845ops/s *1307.7mb/s* 0.0ms/op 20us/op-cpu 1062: 213.628: IO Summary: 4226337 ops, 41845.0 ops/s, (41845/0 r/w) 1307.7mb/s, 21us cpu/op, 0.0ms latency 1062: 213.628: Shutting down processes --------------------------------------------------------------------------------------------- The output looks GREAT so far .... notice...

On 11/12/2015 08:02 PM, Felipe Franciosi wrote: > Hi Jason, > > I understand your busy loop timeout is quite conservative at 50us. Did you try any other values? I've also tried 20us. And results shows 50us was better in: - very small packet tx (e.g 64bytes at most 46% improvement) - TCP_RR (at most 11% improvement) But I will test bigger values. In fact, for net itself, we can be even more aggressive: make vhost poll forever but I haven't tired this. > > Also, did...

This is problem 1 of 3 problems we are having with live migration and/or ACPI on Xen-4.3 and Xen-4.2. Any help would be appreciated. Detailed description of problem: We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud images running 3.2.0-39-virtual. We are using the xl.conf below on qemu-upstream-dm and HVM and

...mpleted in 1us Feb 28 23:07:11 laptop kernel: [ 13.753680] nouveau: DRM:00000000:0000917c: init running... Feb 28 23:07:11 laptop kernel: [ 13.753700] nouveau: DRM:00000000:0000917c: init children... Feb 28 23:07:11 laptop kernel: [ 13.753700] nouveau: DRM:00000000:0000917c: init completed in 20us Feb 28 23:07:11 laptop kernel: [ 13.753716] nouveau: DRM:f0000000:0000003d: init running... Feb 28 23:07:11 laptop kernel: [ 13.753716] nouveau: DRM:f0000000:0000003d: init children... Feb 28 23:07:11 laptop kernel: [ 13.753717] nouveau: DRM:f0000000:0000003d: init completed in 1us Feb 28 23:...

...> Feb 28 23:07:11 laptop kernel: [ 13.753680] nouveau: DRM:00000000:0000917c: init running... > Feb 28 23:07:11 laptop kernel: [ 13.753700] nouveau: DRM:00000000:0000917c: init children... > Feb 28 23:07:11 laptop kernel: [ 13.753700] nouveau: DRM:00000000:0000917c: init completed in 20us > Feb 28 23:07:11 laptop kernel: [ 13.753716] nouveau: DRM:f0000000:0000003d: init running... > Feb 28 23:07:11 laptop kernel: [ 13.753716] nouveau: DRM:f0000000:0000003d: init children... > Feb 28 23:07:11 laptop kernel: [ 13.753717] nouveau: DRM:f0000000:0000003d: init completed in...