similar to: [PATCH 1/2] Fix ixgbe RSS operation

The correct kernel configuration for VMDq support is CONFIG_XEN_NETDEV2_VMQ, not CONFIG_XEN_NETDEV2_BACKEND. Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> diff -urpN a/drivers/net/ixgbe/ixgbe.h b/drivers/net/ixgbe/ixgbe.h --- a/drivers/net/ixgbe/ixgbe.h 2009-02-06 09:03:44.000000000 -0800 +++ b/drivers/net/ixgbe/ixgbe.h 2009-02-10 14:32:57.000000000 -0800 @@ -35,7 +35,7 @@

This patch adds experimental VMDq support (AKA Netchannel2 vmq) to the ixgbe driver. This applies to the Netchannel2 tree, and should NOT be applied to the "normal" development tree. To enable VMDq functionality, load the driver with the command-line parameter VMDQ=<num queues>, as in: $ modprobe ixgbe VMDQ=8 You can then set up PV domains to use the device by modifying your VM

Hello, Is there a HowTo or tutorial about the configuration of VMDq or SR-IOV with XEN? Thanks in advance. Best Regards, -- Houssem MEDHIOUB Research Engineer TELECOM & Management SudParis _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, Did 3.4 come with vmdq, sr-iov, etc.. (netchannel2) support included? If so, is there any documentation available on how to make use of it? Also, these techniques seem like a good way to improve network performance on hardware that supports it, but for folks that want to use iptables and other network management utilities from dom0, will it even be possible anymore since the NICs seem to

[RFC] Virtual Machine Device Queues (VMDq) support on KVM Network adapter with VMDq technology presents multiple pairs of tx/rx queues, and renders network L2 sorting mechanism based on MAC addresses and VLAN tags for each tx/rx queue pair. Here we present a generic framework, in which network traffic to/from a tx/rx queue pair can be directed from/to a KVM guest without any software copy.

[RFC] Virtual Machine Device Queues (VMDq) support on KVM Network adapter with VMDq technology presents multiple pairs of tx/rx queues, and renders network L2 sorting mechanism based on MAC addresses and VLAN tags for each tx/rx queue pair. Here we present a generic framework, in which network traffic to/from a tx/rx queue pair can be directed from/to a KVM guest without any software copy.

The attached patches add vmq (multi-queue) support for netchannel2. (also known as VMDq) These patches were based on a previous implementation written for netchannel1 by Kaushik Kumar Ram. These patches are based on the latest netchannel2 public trees. Patches 1 and 2 are for the Xen tree and patches 3 and 4 for the linux tree. This version provides the basic multi-queue functionality but does

On Fri, Apr 24, 2015 at 9:12 AM, Luke Gorrie <luke at snabb.co> wrote: > - How fast would the new design likely be? This proposal eliminates two things in the path: 1. Compared to vhost_net, it bypasses the host tun driver and network stack, replacing it with direct vhost_net <-> vhost_net data transfer. At this level it's compared to vhost-user, but it's not programmable

On Fri, Apr 24, 2015 at 9:12 AM, Luke Gorrie <luke at snabb.co> wrote: > - How fast would the new design likely be? This proposal eliminates two things in the path: 1. Compared to vhost_net, it bypasses the host tun driver and network stack, replacing it with direct vhost_net <-> vhost_net data transfer. At this level it's compared to vhost-user, but it's not programmable

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am new to XEN. Try to move from vmware and Virtualbox (I use both now). Unfortunately, Debian Squeeze no longer support xen (out of the box no dom0) So I am trying to make it myself. I have installed xen 3.4.2 from source, did make world and installed. Got the kernel source from from the git repository with the xen patches following the xen

Changes since v9: * series re-ordering so make functionality more distinct. Basic vlan filtering is patches 1-4. Support for PVID/untagged vlans is patches 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is still additional egress policy. * Slight simplification to code that extracts the VID from skb. Since we now depend on the vlan module, at the time of input skb_tci is

Another checksum offload problem was reported on xen-users, when using a domU as a firewall: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01150.html It also fails without VLANs. The path from dom0->domU with ip_summed==CHECKSUM_HW/proto_csum_blank==1 is broken. - skb_checksum_setup() assumes that a checksum will definitely be calculated in dev_queue_xmit(), but the

What it is: vhost net is a character device that can be used to reduce the number of system calls involved in virtio networking. Existing virtio net code is used in the guest without modification. There's similarity with vringfd, with some differences and reduced scope - uses eventfd for signalling - structures can be moved around in memory at any time (good for migration) - support memory

What it is: vhost net is a character device that can be used to reduce the number of system calls involved in virtio networking. Existing virtio net code is used in the guest without modification. There's similarity with vringfd, with some differences and reduced scope - uses eventfd for signalling - structures can be moved around in memory at any time (good for migration) - support memory

fallthrough to a separate case/default label break; isn't very readable. Convert pseudo-keyword fallthrough; statements to a simple break; when the next label is case or default and the only statement in the next label block is break; Found using: $ grep-2.5.4 -rP --include=*.[ch] -n "fallthrough;(\s*(case\s+\w+|default)\s*:\s*){1,7}break;" * Miscellanea: o Move or coalesce a

CentOS Errata and Enhancement Advisory 2011:1500 Upstream details at : https://rhn.redhat.com/errata/RHEA-2011-1500.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: e6157db320fb12508062122d1770c002 kmod-ixgbe-PAE-rhel5u7-3.4.8_k-2.el5_7.i686.rpm 69c953ef1602b80066a6d7d3366330b2

Hi list, can somebody fix the bug that the device ixN is missing when the cable mainly the SFP+ module isn't inserted during boot?! Today I connected a new server to our storage system which has 3 ixgbe cards so 6 ports and is freebsd 9 based. Then I have noticed that the link is missing and the free ports were missing from ifconfig. Checking the dmesg revealed the problem. ixN: Hardware

CentOS Errata and Enhancement Advisory 2011:1500 Upstream details at : https://rhn.redhat.com/errata/RHEA-2011-1500.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: a0d68877adf6f19c10f2cb09b7b69b05 kmod-ixgbe-rhel5u7-3.4.8_k-2.el5_7.x86_64.rpm bd7f92440047968f6f74cebcbda88055

Hi! Did anyone encountered some ssl transaction problems with latest version of ixgbe? i had some very strange problem with nodes with private ip (the server with 10 gb interface was masquerading the nodes behind a switch with 10gb and 1 gb interfaces) i used the latest drivers and the ssl conection could be made .. as soon as i used the 2.6.18-308.8.1.el5 driver (3.4.8-k) the problem

CentOS Errata and Enhancement Advisory 2015:1915 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-1915.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 626f3f739478522b7510d177d8d9ccd5aed1c2cc60b9f4660c58c07622e35741 kmod-ixgbe-4.0.3-1.el7_1.x86_64.rpm Source: