similar to: [LINUX] netfront: Cleanup and fix TSO/GSO/CHECKSUM conditionals

This patch adds a new feature called feature-split-event-channels for netfront, enabling it to handle TX and RX events separately. If netback does not support this feature, it falls back to use single event channel. Signed-off-by: Wei Liu <wei.liu2@citrix.com> Reviewed-by: David Vrabel <david.vrabel@citrix.com> --- drivers/net/xen-netfront.c | 173

Frontends are expected to write their protocol ABI to xenstore. Since the protocol ABI defaults to the backend's native ABI, things work fine without that as long as the frontend's native ABI is identical to the backend's native ABI. This is not the case for xen-blkfront running 32-on-64, because its ABI differs between 32 and 64 bit, and thus needs this fix. Based on

Frontends are expected to write their protocol ABI to xenstore. Since the protocol ABI defaults to the backend's native ABI, things work fine without that as long as the frontend's native ABI is identical to the backend's native ABI. This is not the case for xen-blkfront running 32-on-64, because its ABI differs between 32 and 64 bit, and thus needs this fix. Based on

add xenbus token support and separate watch event queues Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> # HG changeset patch # User Samuel Thibault <samuel.thibault@eu.citrix.com> # Date 1200582503 0 # Node ID 112c1180720c87a0bfa99142399e3ef3f79f1711 # Parent 33d1c7f9217a1c915afe01fe822811ce69b3a90f add xenbus token support and separate watch event queues diff -r

Unfortunately we managed to not catch in our automatic testing this oversight during the porting of the corresponding pv-ops patch (info->irq now getting set later, which doesn''t matter for pv-ops as that has the event channel at hand). Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/drivers/xen/fbfront/xenfb.c +++ b/drivers/xen/fbfront/xenfb.c @@ -757,7 +757,7 @@ static

This patch cleans up some 80-odd warnings I was seeing when compiling the xenpci driver, all completely trivial. It also replaces the use of asm for calling cpuid with the __cpuid compiler intrinsic, and modifies calling code accordingly. I''m pretty sure my mailer going to mangle the inline patch (below) so I''m attaching the pristine version. (will try to fix for next time) --

Netback and netfront only use one event channel to do tx / rx notification. This may cause unnecessary wake-up of process routines. This patch adds a new feature called feautre-split-event-channel to netback, enabling it to handle Tx and Rx event separately. Netback will use tx_irq to notify guest for tx completion, rx_irq for rx notification. If frontend doesn''t support this feature,

This patch contains fixes for persistent grants implementation v2: * handle == 0 is a valid handle, so initialize grants in blkback setting the handle to BLKBACK_INVALID_HANDLE instead of 0. Reported by Konrad Rzeszutek Wilk. * new_map is a boolean, use "true" or "false" instead of 1 and 0. Reported by Konrad Rzeszutek Wilk. * blkfront announces the

Not tested in any way. The original code for offload setting seems broken as it resets the features on every netback reconnect. This will set GSO_ROBUST at device creation time (earlier than connect time). RX checksum offload is forced on - so advertise as it is. Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- [I don't know Xen code enough to say this is correct. There

Not tested in any way. The original code for offload setting seems broken as it resets the features on every netback reconnect. This will set GSO_ROBUST at device creation time (earlier than connect time). RX checksum offload is forced on - so advertise as it is. Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- [I don't know Xen code enough to say this is correct. There

Not tested in any way. The original code for offload setting seems broken as it resets the features on every netback reconnect. This will set GSO_ROBUST at device creation time (earlier than connect time). RX checksum offload is forced on - so advertise as it is. Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- [I don't know Xen code enough to say this is correct. There

Seems like an oversight that we have set-tx-csum and set-sg hooked up, but not set-tso. Also leads to the strange situation that if you e.g. disable tx-csum, then tso doesn't get disabled. Signed-off-by: Mark McLoughlin <markmc at redhat.com> --- drivers/net/virtio_net.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/net/virtio_net.c

Hi, What's the correct way to disble TSO (TCP Segmentation Offload) in RHEL5? I have tried adding those options in ifcfg-ethX configuration file: # grep ETHTOOL /etc/sysconfig/network-scripts/ifcfg-eth0 ETHTOOL_OPTS="tso off" And also with: ETHTOOL_OPTS="-K eth0 tso off" But when restating the server TSO is enabled: # ethtool -k eth0 tcp segmentation offload: on As

Hello, Writing to seek help in regard to some unexpected performance anomaly i am observing in using tsoutlers:tso on the mac vs on an AWS cloud server.. I am running the following code with very small dataset of about 208 records. d.dir <- '/Users/darshanpandya/xxxxxx' FNAME <- 'my_data.csv' d.input <- fread(file.path(paste0(d.dir,"/zzz/"),FNAME,fsep =

Seems like an oversight that we have set-tx-csum and set-sg hooked up, but not set-tso. Also leads to the strange situation that if you e.g. disable tx-csum, then tso doesn't get disabled. Signed-off-by: Mark McLoughlin <markmc at redhat.com> --- drivers/net/virtio_net.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/net/virtio_net.c

We've been encountering an issue in the virtio-net driver that cause it to become unresponsive after a period of high load. This issue goes away if we disable TSO on the interface. Once this issue has been triggered, the interface can still receive traffic, but will not transmit anything. Specifically: * Initially the machine will still try to respond to packets (I say try, because I

I am trying to turn ON TSO in my Ubuntu Virtual machine but it gives me the following error: [image: image.png] Also on doing *ethtool -k ens3* all the features are marked as [fixed]. How to use libvirt to configure VM to have TSO?

We've been encountering an issue in the virtio-net driver that cause it to become unresponsive after a period of high load. This issue goes away if we disable TSO on the interface. Once this issue has been triggered, the interface can still receive traffic, but will not transmit anything. Specifically: * Initially the machine will still try to respond to packets (I say try, because I

Hi, I see you all agree to apply :) Stephen, repost of this patch to proper places below. Thank you Henrik for clarification of bridge standard. However, silent drop of locally generated packets on 99% idle carrier grade machine looks like a hardware problem. David, don't you think that having software packet drop counters is a bad idea? I thought, software drop counters are there to help

Since virtio does not provide it's own ndo_features_check handler, TSO, and now checksum offload, are disabled for stacked vlans. Re-enable the support and let the host take care of it. This restores/improves Guest-to-Guest performance over Q-in-Q vlans. CC: "Michael S. Tsirkin" <mst at redhat.com> CC: Jason Wang <jasowang at redhat.com> CC: virtualization at