similar to: [PATCH] Fix bashism in scripts/Makefile.xen

Hi Keir: [NET] front: Fix features on resume when csum is off When the netfront driver is resumed the features are renegotiated with the backend. However, I forgot take into account the status of the TX checksum setting. When TX checksum is disabled by the user, we cannot enable SG or TSO since both require checksum offload. This patch makes xennet check the checksum setting before

On Thu, Oct 27, 2005 at 10:22:08PM -0700, H. Peter Anvin wrote: > > >So it looks like as long as dash can link with klibc then: OK, I've got it to build with klibc using klcc: $ size src/dash text data bss dec hex filename 63333 356 5940 69629 10ffd src/dash Unfortunately there seems to be something fishy in parameter expansion as it fails three

Hi Keir: It has been brought to my attention that modular oprofile is broken because it now calls get_vm_area which is not an exported function. This appears to be the result of the changeset that removed vm_map_xen_pages which was only used by oprofile. So we either need to export get_vm_area in Xen, or put that function back. What do you think about this? Thanks, -- Visit Openswan at

Hi: I noticed a bug in the realloc error checking code in the QEMU backend for RealTek8139. However, what''s worse is that there is no cap on the total size of the transmit buffer at all. So a guest can keep extending it until memory runs out. CP_TX_BUFFER_SIZE is already 64K. So it seems to me that we don''t need the while loop to extend the buffer at all since no transmitted

Hi: Here are the patches I used for testing KVM with virtio-net using TSO. There are three patches for the tun device which are basically Rusty's patches with the mmap turned into copying (for correctness). Two patches are for the virtio-net frontend, one required to support receiving SG/TSO, and the other useful for testing SG per se. The other patch is to the KVM backend to make all this

Hi: Here are the patches I used for testing KVM with virtio-net using TSO. There are three patches for the tun device which are basically Rusty's patches with the mmap turned into copying (for correctness). Two patches are for the virtio-net frontend, one required to support receiving SG/TSO, and the other useful for testing SG per se. The other patch is to the KVM backend to make all this

Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it

fix subject and added warning to patch mail, thanks for review. ----- Forwarded message from "H. Peter Anvin" <hpa at zytor.com> ----- Date: Mon, 29 Mar 2010 15:07:01 -0700 From: "H. Peter Anvin" <hpa at zytor.com> To: maximilian attems <max at stro.at> Cc: Colin Watson <cjwatson at ubuntu.com>, klibc at zytor.com, Herbert Xu <herbert at

----- Forwarded message from "H. Peter Anvin" <hpa at zytor.com> ----- Date: Mon, 29 Mar 2010 15:07:01 -0700 From: "H. Peter Anvin" <hpa at zytor.com> To: maximilian attems <max at stro.at> Cc: Colin Watson <cjwatson at ubuntu.com>, klibc at zytor.com, Herbert Xu <herbert at gondor.apana.org.au>, Nobuhiro Iwamatsu <iwamatsu at nigauri.org>

Hi Herbert, I wonder if you''ve got a chance to look at netfront in light of the new stuff in davem''s network tree (the stuff that''s in http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.22.git). In particular, struct sk_buff has been changed so that "nh" has gone, and the replacement can be just an offset rather than a full pointer. This breaks the

This effectively reverts 99ffc696d10b28580fe93441d627cf290ac4484c "virtio: wean net driver off NETDEV_TX_BUSY". The complexity of queuing an skb (setting a tasklet to re-xmit) is questionable, especially once we get rid of the other reason for the tasklet in the next patch. If the skb won't fit in the tx queue, just return NETDEV_TX_BUSY. It might be frowned upon, but it's

This effectively reverts 99ffc696d10b28580fe93441d627cf290ac4484c "virtio: wean net driver off NETDEV_TX_BUSY". The complexity of queuing an skb (setting a tasklet to re-xmit) is questionable, especially once we get rid of the other reason for the tasklet in the next patch. If the skb won't fit in the tx queue, just return NETDEV_TX_BUSY. It might be frowned upon, but it's

On Thu, Apr 16, 2009 at 01:08:18AM -0000, Herbert Xu wrote: > On Wed, Apr 15, 2009 at 10:38:34PM +0800, Herbert Xu wrote: > > > > So how about this? We replace the dev destructor with our own that > > doesn't immediately call free_netdev. We only call free_netdev once > > all tun fd's attached to the device have been closed. > > Here's the patch.

On Thu, Apr 16, 2009 at 01:08:18AM -0000, Herbert Xu wrote: > On Wed, Apr 15, 2009 at 10:38:34PM +0800, Herbert Xu wrote: > > > > So how about this? We replace the dev destructor with our own that > > doesn't immediately call free_netdev. We only call free_netdev once > > all tun fd's attached to the device have been closed. > > Here's the patch.

Peter, i ask you to permit discussion of `dash' in the klibc list. Pulled reasons are, that bugs and followups are distributed in bug tracking systems with arbitrary decisions. In the klibc there are also changes, that can be discussed widely, and opinions with possible solutions published. So far i have two problems. First is proposed change for test(1):

Greetings all, I've setup a new gretap device as per Herbert Xu's new patches and it works as expected for smaller MTU. I'm wondering if gretap tunnels handle fragmentation at all or if this might be a bridge related issue. The same setup works quite well if I use vtun with a tap device however, so while this isn't entirely bridge-related, Maybe someone here might have

Nick Piggin <npiggin@suse.de> wrote: > > Also, for non-wb memory. I don't think the Intel document referenced > says anything about this, but the AMD document says that loads can pass > loads (page 8, rule b). > > This is why our rmb() is still an lfence. BTW, Xen (in particular, the code in drivers/xen) uses mb/rmb/wmb instead of smp_mb/smp_rmb/smp_wmb when it

Nick Piggin <npiggin@suse.de> wrote: > > Also, for non-wb memory. I don't think the Intel document referenced > says anything about this, but the AMD document says that loads can pass > loads (page 8, rule b). > > This is why our rmb() is still an lfence. BTW, Xen (in particular, the code in drivers/xen) uses mb/rmb/wmb instead of smp_mb/smp_rmb/smp_wmb when it

This patch is cleaned up of the patch which was sent as http://lists.xensource.com/archives/html/xen-devel/2007-06/msg00324.html # HG changeset patch # User yamahata@valinux.co.jp # Date 1181545986 -32400 # Node ID 69e2dd4e06c405a92717c5f1818f5096e1dc0bcd # Parent d5e0eb7dd069c0ffc1854da81aa143ccfb0ad66e make dma address conversion logic of gnttab dma arch specific. gnttab_dma_map_page() and

An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20080714/a884a437/attachment.txt