similar to: Reg: Throughput b/w domU & dom0

Hi all, I used netperf to measure throughput between dom0 & domU. The throughput between dom0 -> domU was 256.00 Mb/sec domU -> dom0 was 401.15 Mb/sec. The throughput between dom0 & domU seems to be very asymmetry. To my surprise the throughput between domU -> dom0 is more. The value which I specified are consistent values. Is

Hi all, I used netperf to measure throughput between dom0 & domU. The throughput between dom0 -> domU was 256.00 Mb/sec domU -> dom0 was 401.15 Mb/sec. 1) Dom0 -> DomU: Recv Socket Size bytes Send Socket Size bytes Send Message Size bytes Elapsed Time Secs. Throughput Mbs/sec 87380 16384 16384 10.01 231.61

Hi all, I used netperf to measure throughput between dom0 & domU. The throughput between dom0 -> domU was 256.00 Mb/sec domU -> dom0 was 401.15 Mb/sec. 1) Dom0 -> DomU: Recv Socket Size bytes Send Socket Size bytes Send Message Size bytes Elapsed Time Secs. Throughput Mbs/sec 87380 16384 16384 10.01 231.61

Hi Is there anyone who has successfully resolved the low throughput problem in Guest communication. I am using Xen3.4.1 with PV os kernel 2.6.30-rc6-tip On fedora11. While running netperf benchmark on guests throughput results are very low DomU to DomU    0.29 Mbps Why is it so? What would be the problem. Is there any issue with fc11 platform? Regards, Fasiha Ashraf Add whatever you love

I am using a 2.6.35 domU guest on a 2.6.32 dom0 and a 4.0.1 Xen hypervisor. Using netperf with UDP_RR I get 1819 and 622 transaction per second for domU and dom0 respectively, but in UDP_STREAM test domU is showing a better throughput for all packet sizes (on average around 3Mbps better, on a 10/100 network with around 96Mbps average native throuput). Is it normal or I am missing something?

hi, Is asterisk a registrar server. thanks, satish Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately and

Hi We are using Samba-3.0alpha23. And we are facing 2 problems related to it. We have used the default configuration setting provided in configuration file of samba-3.0alpha23. 1 ) Refresh Functionality not working We have installed samba-3.0alpha23 and are using it to access the printer installed on Linux machine. When we connect from two windows client and give a print. The status is not

I have set-up xen on my Intel quad core server. Now running different experiment to measure network throughput in virtualized environment. these are some of the results: Netperf-4.5 results for inter-domain communication. Sr.No.              Client               Server               Time(sec)        Throughput(Mbps)    1                   Guest-1              Dom0                   

Hi, I am encountering a weird issue, where domU RX throughput (of traffic from another machine) is very low. But domU RX throughput from dom0 is fine, and dom0 RX from another machine is fine. iperf reported the following throughputs: dom0 <- outside -- 942Mbps domU <- dom0 -- 3467Mbps domU <- outside -- 87Mbps The NIC on the machine is 1GE. What puzzles me is, some instances of domU

"yum update" has been run first on CentOS 5.1 box. ************************ Installation profile : ************************ name = "Solaris81PVM" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-81" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/03/15 08:42 PM, Marcelo Ricardo Leitner wrote: > On 12-03-2015 17:39, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 12/03/15 04:29 PM, Gilbert Sebenste wrote: >>> Hello everyone, >>> >>> A network engineer buddy of mine brought up for discussion with >>> me

On 12-03-2015 17:39, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/03/15 04:29 PM, Gilbert Sebenste wrote: >> Hello everyone, >> >> A network engineer buddy of mine brought up for discussion with me >> that he'd like to do some throughput testing, but he's new to >> Linux/RedHat. Is there any software I can recommend to

Hey Guys, when starting a DomU we use iscsi as disks for our vms. When testing throughput I get half the troughput in contrast to tests on the Dom0 itself. For Example: I log in the target on the xenhost (Dom0) itself and get a troughput of 80mb/s. that''s ok Now im starting the VM (DomU) and the same target is now attached as xvdb. When doing troughput tests the speed is about

box. I'll send an updated KVM tools patch in a bit as well. Before: # netperf -H 192.168.33.4,ipv4 -t TCP_RR MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.33.4 (192.168.33.4) port 0 AF_INET : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size Size Time Rate bytes Bytes bytes bytes

box. I'll send an updated KVM tools patch in a bit as well. Before: # netperf -H 192.168.33.4,ipv4 -t TCP_RR MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.33.4 (192.168.33.4) port 0 AF_INET : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size Size Time Rate bytes Bytes bytes bytes

Hi, We have been using Samba File Server (Version 4.3.11 Ubuntu 14.04 LTS) for quite sometime now. We recently installed Samba-AD (Samba AD Version 4.7.6) and made the file server a member of the Domain. Everything was fine till around 11:15 am yesterday. We just added one more share folder and gave access to three users and restarted Samba File Server services - smbd, nmbd and winbindd -

Hi Looks like 1.1 version is sensitive to the system architecture/compiler/kernel version. Below is my observation in various linux system I have. As you mentioned, you are not observed the crash in your system, can you please share your system details. And also please comment on the below table/observations. *Machine IP* *optimization flags* *RHEL version* *kernel version* *gcc version*

I just tried decoding with v1.1: ./opus_demo -d 48000 2 opus_encoded_crash.opus out.pcm and I see no issue (including with valgrind). Does the same command-line create problems for you? What compile flags did you use? fixed-point or float, any assembly, ...? Could be assembly here, or even a compiler bug wouldn't be unheard of. Cheers, Jean-Marc On 20/04/15 07:27 AM, Suresh Thiriveedi

Still can't reproduce. What OS and compiler version? Jean-Marc On 21/04/15 02:48 AM, Suresh Thiriveedi wrote: > Hi, > > There is no change in the compiler flags. I'm using as it is from the > original code. No change in the Makefile and I believe it is using the > floating point only by default. > > We are using 8k samples and mono so the commands is as follows.

Hi, In rpcclient/cmd_spoolss.c line 1715 & 1718 struct cmd_set spoolss_commands[] = { { "SPOOLSS" }, . . { "getprintprocdir", cmd_spoolss_getprintprocdir, PIPE_SPOOLSS, "Get print processor directory", "" }, . . { "getprintprocdir", cmd_spoolss_getprintprocdir, PIPE_SPOOLSS, "Get print processor directory",