similar to: [PATCH] Log error in csum dev_queue_xmit error path

Hello Xen folks, I have independently verified that this patch indeed fixes the issue (I posted a message about the issue over the summer: http://lists.xensource.com/archives/html/xen-devel/2005-08/msg00114.html). I used changeset 8911 of xen-unstable.hg. The patch as written expects kernel linux-2.6.16-rc2, but changeset 8911 uses kernel 2.6.16-rc4. I verified that the patch works with

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

Below is a fix for the current problem of checksum offload not working in a NAT''ed network. The cause is the NAT/iptables code incorrectly modifying the TCP/UDP checksum (for the checksum offload case). The original code assumes a valid checksum, which is not the case for checksum offload packets (which has a complimented, partial checksum for the hardware to use). The fix is to

Libvirt has a fixed 15 second timeout for qemu to exit. If qemu is writing to a slow USB key, it can hang (in D state) for much longer than this - many minutes usually. To work around this, fsync the output file before closing the libvirt connection so that qemu shouldn't have anything (much) to write. We have to do this in a few places in the code. This is a hack - it would be better to

> It appears that when alloc''ing a skb, it is bring padded by > an arbitrarily > (and excessive) long value. The value for this padding > really only needs to > be 24. 24 = 14 for the ethernet header + 2 for the cache > alignment + 4 for > the CRC + 4 for the VLAN flags. Given that we''re allocating page sized buffers the current situation

This patch enables x86-64 Xen dom0 to compile if IOMMU is enabled in the kernel config. Warning, dom0 will crash during boot of the kernel if IOMMU is enabled. These changes do not affect non-IOMMU enabled kernels (a fact I have verified myself). I am currently working on debugging the IOMMU dom0 crash. Signed-off-by: Jon Mason <jdmason@us.ibm.com> ---

I''m a noob to rails and i could use some help. Fedora Core 5 Ruby 1.8.4 Rails 1.1.2 Postgres for My Database Using webrick for testing at the monent but have lighttpd installed but the service is diabled. Here are my steps that i fillow. In my home directory i type rails test #cd test #sudo chmod -R 775 log #sudo chmod -R 775 public #ruby script/server Then i make my postgres database

--- "Olle E. Johansson" <oej@edvina.net> wrote: > From: "Olle E. Johansson" <oej@edvina.net> > To: asterisk-users@lists.digium.com > Subject: Re: [Asterisk-Users] Asterisk on FreeBSD > Date: Mon, 27 Oct 2003 08:24:22 +0100 > > Rich Adamson wrote: > > >>My Asterisk (fresh CVS) takes 98% of the system load on my FreeBSD > server.

Hi Sambafriends ! I have done a migration from Novell to a Samba-PDC in a medium enterprise with nearly 50 workstations eight weeks ago. After a couple of problems the most things run well. But i have a few questions left and it would be nice, if an experienced user can help me: When i look at the /var/log/warn listing i still see some errors, and i like to ask you, if this messages are

Hello all! First of all - I very new to Samba and don't really sure what i do all right. I'm ask some advise from community. I'm make this configuration in my company: PDC + Master LDAP: smb.conf: [global] # Base workgroup = hq netbios name = dc server string = DC Server security = domain hosts allow = 172.16.1. 192.168.1. 127. encrypt passwords = yes admin

Hello. Time after time users can not log in in domain and im see this in logs(time stamps deleted): nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup HQ on subnet 172.16.1.3 ...skipping... nmbd/nmbd_incomingrequests.c:process_name_release_request(80) process_name_release_request: unicast name release request

We don't support partial csumed packet since its metadata will be lost or incorrect during XDP processing. So fail the XDP set if guest_csum feature is negotiated. Fixes: f600b6905015 ("virtio_net: Add XDP support") Reported-by: Jesper Dangaard Brouer <brouer at redhat.com> Cc: Jesper Dangaard Brouer <brouer at redhat.com> Cc: Pavel Popa <pashinho1990 at gmail.com>

From: Jason Wang <jasowang at redhat.com> Date: Thu, 22 Nov 2018 14:36:30 +0800 > We don't disable VIRTIO_NET_F_GUEST_CSUM if XDP was set. This means we > can receive partial csumed packets with metadata kept in the > vnet_hdr. This may have several side effects: > > - It could be overridden by header adjustment, thus is might be not > correct after XDP processing.

On Mon, Sep 28, 2020 at 5:41 AM <xiangxia.m.yue at gmail.com> wrote: > > From: Tonghao Zhang <xiangxia.m.yue at gmail.com> > > Open vSwitch and Linux bridge will disable LRO of the interface > when this interface added to them. Now when disable the LRO, the > virtio-net csum is disable too. That drops the forwarding performance. > > Fixes: e59ff2c49ae1

On Mon, Sep 28, 2020 at 11:39:14AM +0800, xiangxia.m.yue at gmail.com wrote: > From: Tonghao Zhang <xiangxia.m.yue at gmail.com> > > Open vSwitch and Linux bridge will disable LRO of the interface > when this interface added to them. Now when disable the LRO, the > virtio-net csum is disable too. That drops the forwarding performance. > > Fixes: e59ff2c49ae1

On Tue, Sep 29, 2020 at 09:40:22AM +0800, Tonghao Zhang wrote: > On Tue, Sep 29, 2020 at 3:21 AM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Mon, Sep 28, 2020 at 11:39:14AM +0800, xiangxia.m.yue at gmail.com wrote: > > > From: Tonghao Zhang <xiangxia.m.yue at gmail.com> > > > > > > Open vSwitch and Linux bridge will disable LRO of

On Tue, Sep 29, 2020 at 09:58:06AM +0800, xiangxia.m.yue at gmail.com wrote: > From: Tonghao Zhang <xiangxia.m.yue at gmail.com> > > Open vSwitch and Linux bridge will disable LRO of the interface > when this interface added to them. Now when disable the LRO, the > virtio-net csum is disable too. That drops the forwarding performance. > > Fixes: a02e8964eaf9

On Tue, Sep 29, 2020 at 02:59:03PM +0800, Tonghao Zhang wrote: > On Tue, Sep 29, 2020 at 2:23 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Tue, Sep 29, 2020 at 09:58:06AM +0800, xiangxia.m.yue at gmail.com wrote: > > > From: Tonghao Zhang <xiangxia.m.yue at gmail.com> > > > > > > Open vSwitch and Linux bridge will disable LRO of

On Tue, Sep 29, 2020 at 4:00 AM <xiangxia.m.yue at gmail.com> wrote: > > From: Tonghao Zhang <xiangxia.m.yue at gmail.com> > > Open vSwitch and Linux bridge will disable LRO of the interface > when this interface added to them. Now when disable the LRO, the > virtio-net csum is disable too. That drops the forwarding performance. I had focused on the code previously.

>From the manpage: --csum-length=LENGTH By default the primary checksum used in rsync is a very strong 16 byte MD4 checksum. In most cases you will find that a trun- cated version of this checksum is quite efficient, and this will decrease the size of the checksum data sent over the link, mak- ing things faster. You can choose the