search for: vmxnet3

...nd also free resources accordingly. This fixes the kernel panic reported by Tetsuo Handa. Version bumped to 1.2.1.0 Acked-by: Shelley Gong <shelleygong at vmware.com> Acked-by: Bhavesh Davda <bhavesh at vmware.com> Signed-off-by: Andy King <acking at vmware.com> --- drivers/net/vmxnet3/vmxnet3_drv.c | 14 ++++++++------ drivers/net/vmxnet3/vmxnet3_int.h | 4 ++-- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/drivers/net/vmxnet3/vmxnet3_drv.c b/drivers/net/vmxnet3/vmxnet3_drv.c index d6e90c7..f450010 100644 --- a/drivers/net/vmxnet3/vmxnet3_drv.c +++ b/drive...

...nd also free resources accordingly. This fixes the kernel panic reported by Tetsuo Handa. Version bumped to 1.2.1.0 Acked-by: Shelley Gong <shelleygong at vmware.com> Acked-by: Bhavesh Davda <bhavesh at vmware.com> Signed-off-by: Andy King <acking at vmware.com> --- drivers/net/vmxnet3/vmxnet3_drv.c | 14 ++++++++------ drivers/net/vmxnet3/vmxnet3_int.h | 4 ++-- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/drivers/net/vmxnet3/vmxnet3_drv.c b/drivers/net/vmxnet3/vmxnet3_drv.c index d6e90c7..f450010 100644 --- a/drivers/net/vmxnet3/vmxnet3_drv.c +++ b/drive...

...rces accordingly. Version bumped to 1.2.1.0 Acked-by: Shelley Gong <shelleygong at vmware.com> Acked-by: Bhavesh Davda <bhavesh at vmware.com> Signed-off-by: Andy King <acking at vmware.com> Reported-by: Tetsuo Handa <penguin-kernel at I-love.SAKURA.ne.jp> --- drivers/net/vmxnet3/vmxnet3_drv.c | 15 ++++++++------- drivers/net/vmxnet3/vmxnet3_int.h | 4 ++-- 2 files changed, 10 insertions(+), 9 deletions(-) diff --git a/drivers/net/vmxnet3/vmxnet3_drv.c b/drivers/net/vmxnet3/vmxnet3_drv.c index d6e90c7..6dfcbf5 100644 --- a/drivers/net/vmxnet3/vmxnet3_drv.c +++ b/driv...

Hi, Could CentOS kernel keepers apply following patch on current kernel? http://patchwork.ozlabs.org/patch/95785/ (Current as: 2.6.32-71.29.1.el6.x86_64) With the patch applied, and a ".local" kernel built, I get 30% higher throughput with vmxnet3 in my IP routing node, than when using e1000 "card" at the same. Without the patch, the TCP flow over vmxnet3 driver on a _router_ node is abysmally slow. I am running a bunch of CentOS servers on VMware ESXi 4.1U1 hosts with multiple of VLANs. The best network performance is obtainable...

This version addresses Sergei's comments. o Fixed description and added Reported-by o Removed NULL check for kfree()

This version addresses Sergei's comments. o Fixed description and added Reported-by o Removed NULL check for kfree()

...e if there's something wrong there. Best, Patrick <<< I've been working on this issue, I have tested the timers, and as you guys mentioned before they are OK. I've noticed that if the VMware VM uses the driver e1000e everything is "OK" but if the VM uses the "vmxnet3" the problem is there. I have attached a small pcap file showing the end of the lpxelinux.0 TFTP transfer and the beginning of the problematic ldlinux.c32 transfer. I wonder if the "vmxnet3" driver is probably "too fast" for the Sequential lwIP API? Best, Patrick ------...

...drive the underlying physical device. VMware has been exploring various ways to deliver this technology to users in a manner which is easy to adopt. In this process we have prepared an architecture along with Intel - NPA (Network Plugin Architecture). NPA allows the guest to use the virtualized NIC vmxnet3 to passthrough to a number of physical NICs which support it. The document below provides an overview of NPA. We intend to upgrade the upstreamed vmxnet3 driver to implement NPA so that Linux users can exploit the benefits provided by passthrough devices in a seamless manner while retaining the be...

...drive the underlying physical device. VMware has been exploring various ways to deliver this technology to users in a manner which is easy to adopt. In this process we have prepared an architecture along with Intel - NPA (Network Plugin Architecture). NPA allows the guest to use the virtualized NIC vmxnet3 to passthrough to a number of physical NICs which support it. The document below provides an overview of NPA. We intend to upgrade the upstreamed vmxnet3 driver to implement NPA so that Linux users can exploit the benefits provided by passthrough devices in a seamless manner while retaining the be...

...irtual IOMMU. We need to add IOMMU mappings for such DMAs to work correctly. Fix that with pci_alloc_consistent() where possible, or pci_map_single() where the mapping is short-lived or we don't control the allocation (netdev). Also fix two small bugs: 1) use after free of rq->buf_info in vmxnet3_rq_destroy() 2) a cpu_to_le32() that should have been a cpu_to_le64() Acked-by: George Zhang <georgezhang at vmware.com> Acked-by: Aditya Sarwade <asarwade at vmware.com> Signed-off-by: Andy King <acking at vmware.com> --- drivers/net/vmxnet3/vmxnet3_drv.c | 89 +++++++++++++++...

...irtual IOMMU. We need to add IOMMU mappings for such DMAs to work correctly. Fix that with pci_alloc_consistent() where possible, or pci_map_single() where the mapping is short-lived or we don't control the allocation (netdev). Also fix two small bugs: 1) use after free of rq->buf_info in vmxnet3_rq_destroy() 2) a cpu_to_le32() that should have been a cpu_to_le64() Acked-by: George Zhang <georgezhang at vmware.com> Acked-by: Aditya Sarwade <asarwade at vmware.com> Signed-off-by: Andy King <acking at vmware.com> --- drivers/net/vmxnet3/vmxnet3_drv.c | 89 +++++++++++++++...

This patch adds support for virtual IOMMU to the vmxnet3 module. We switch to DMA consistent mappings for anything we pass to the device. There were a few places where we already did this, but using pci_blah(); these have been fixed to use dma_blah(), along with all new occurrences where we've replaced kmalloc() and friends. Also fix two small bugs...

This patch adds support for virtual IOMMU to the vmxnet3 module. We switch to DMA consistent mappings for anything we pass to the device. There were a few places where we already did this, but using pci_blah(); these have been fixed to use dma_blah(), along with all new occurrences where we've replaced kmalloc() and friends. Also fix two small bugs...

...wrong or is it not possible to accomplish this >> scenario?? > > Here are my old notes how to run ESXi6 on KVM on Fedora 21: > > # cat /etc/modprobe.d/nested.conf > options kvm ignore_msrs=1 > options kvm-intel nested=y ept=y > > > Install ESXI6 Hypervisor with the vmxnet3 nic: > > # virt-install --connect=qemu:///system -n esxi6 --cpu=host --vcpus=2 > --ram 4096 --os-type=linux > --cdrom=/var/lib/libvirt/images/VMware-VMvisor-Installer-6.0.0-2494585.x86_64.iso > --disk > path=/var/lib/libvirt/images/esxi6.qcow2,format=qcow2,bus=ide,size=25,cache=no...

...> Cc: "VMware, Inc." <pv-drivers at vmware.com> Cc: Francois Romieu <romieu at fr.zoreil.com> Cc: virtualization at lists.linux-foundation.org Cc: netdev at vger.kernel.org Cc: xen-devel at lists.xensource.com --- drivers/net/virtio_net.c | 2 +- drivers/net/vmxnet3/vmxnet3_drv.c | 2 +- drivers/net/wan/dscc4.c | 2 +- drivers/net/wan/farsync.c | 2 +- drivers/net/wan/lmc/lmc_main.c | 2 +- drivers/net/xen-netfront.c | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_...

...> Cc: "VMware, Inc." <pv-drivers at vmware.com> Cc: Francois Romieu <romieu at fr.zoreil.com> Cc: virtualization at lists.linux-foundation.org Cc: netdev at vger.kernel.org Cc: xen-devel at lists.xensource.com --- drivers/net/virtio_net.c | 2 +- drivers/net/vmxnet3/vmxnet3_drv.c | 2 +- drivers/net/wan/dscc4.c | 2 +- drivers/net/wan/farsync.c | 2 +- drivers/net/wan/lmc/lmc_main.c | 2 +- drivers/net/xen-netfront.c | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_...

Hi, I try to install a VMware VM via virsh with a vmxnet3 network card. Virsh sends me an error : "Insufficient video RAM. The maximum resolution of the virtual machine will be limited to 1176x885. To use the configured maximum resolution of 2560x1600, increase the amount of video RAM allocated to this virtual machine by setting svga.vramSize=&...

...opy). >>> >> It would be an interesting idea if we didn't already have the vhost >> model where we don't need the userspace bounce. > > The model is very interesting for QEMU because then we can use vhost as > a backend for other types of network adapters (like vmxnet3 or even > e1000). > > It also helps for things like fault tolerance where we need to be able > to control packet flow within QEMU. (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). Then I'm really confused as to what this would look like. A zero copy...

...opy). >>> >> It would be an interesting idea if we didn't already have the vhost >> model where we don't need the userspace bounce. > > The model is very interesting for QEMU because then we can use vhost as > a backend for other types of network adapters (like vmxnet3 or even > e1000). > > It also helps for things like fault tolerance where we need to be able > to control packet flow within QEMU. (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). Then I'm really confused as to what this would look like. A zero copy...

hyperv_net: - set min/max_mtu virtio_net: - set min/max_mtu - remove virtnet_change_mtu vmxnet3: - set min/max_mtu CC: netdev at vger.kernel.org CC: virtualization at lists.linux-foundation.org CC: "K. Y. Srinivasan" <kys at microsoft.com> CC: Haiyang Zhang <haiyangz at microsoft.com> CC: "Michael S. Tsirkin" <mst at redhat.com> CC: Shrikrishna Khare &lt...