similar to: [PATCH next] xen: Use more current logging styles

Tune xen_netbk_count_requests to not touch working array beyond limit, so that we can make working array size constant. Signed-off-by: Wei Liu <wei.liu2@citrix.com> --- drivers/net/xen-netback/netback.c | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c index

There is a typo here, "i" vs "j", so we would crash on module_exit(). Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c index a0b50ad..130bcb2 100644 --- a/drivers/net/xen-netback/netback.c +++ b/drivers/net/xen-netback/netback.c @@ -1968,8 +1968,8 @@ static void __exit

VM traffic is already limited by a throughput limit, but there is no control over the maximum packet per second (PPS). In DDOS attack the major issue is rather PPS than throughput. With provider offering more bandwidth to VMs, it becames easy to coordinate a massive attack using VMs. Example: 100Mbits ~ 200kpps using 64B packets. This patch provides a new option to limit VMs maximum packets per

Add xen-backend:vif module alias to the xen-netback module. This allows automatic loading of the module. Signed-off-by: Bastian Blank <waldi at debian.org> Acked-by: Ian Campbell <ian.campbell at citrix.com> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> --- drivers/net/xen-netback/netback.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git

Add xen-backend:vif module alias to the xen-netback module. This allows automatic loading of the module. Signed-off-by: Bastian Blank <waldi at debian.org> Acked-by: Ian Campbell <ian.campbell at citrix.com> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> --- drivers/net/xen-netback/netback.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git

Add xen-backend:vif module alias to the xen-netback module. This allows automatic loading of the module. Signed-off-by: Bastian Blank <waldi at debian.org> Acked-by: Ian Campbell <ian.campbell at citrix.com> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> --- drivers/net/xen-netback/netback.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git

Hi, Ubuntu 10.04 x64 installing xen4.0 testing when compiling kernel 2.6.32.16 from jeremy git i get this error: WARNING: modpost: Found 7 section mismatch(es). To see full details build your kernel with: ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD

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,

We''ve been hitting the following issue on a variety of hosts and recent Xen/dom0 version combinations. Here''s an excerpt from our latest: Xen: 4.1.4 (xenbits @ 23432) Dom0: 3.7.1-x86_64 BUG: unable to handle kernel NULL pointer dereference at 000000000000001c IP: [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ebt_comment

When counting required slots for skb, netback directly uses DIV_ROUND_UP to get slots required by header data. This is wrong when offset in the page of header data is not zero, and is also inconsistent with following calculation for required slot in netbk_gop_skb. In netbk_gop_skb, required slots are calculated based on offset and len in page of header data. It is possible that required slots

This is netback multithread support patchset version 4. Main Changes from v3: 1. Patchset is against xen/next tree. 2. Merge group and idx into netif->mapping. 3. Use vmalloc to allocate netbk structures. Main Changes from v2: 1. Merge "group" and "idx" into "netif->mapping", therefore page_ext is not used now. 2. Put netbk_add_netif() and netbk_remove_netif()

Hi, We are running into a situation where rsp_prod index in the shared ring is not getting updated for the netfront tx ring by the netback. We see that rsp_cons is the same value as rsp_prod, with req_prod 236 slots away(tx ring is full). From looking at the netfront driver code, it looks as if xennet_tx_buf_gc processing only happens if rsp_prod is more than rsp_cons. Our

Hi, We are running into a situation where rsp_prod index in the shared ring is not getting updated for the netfront tx ring by the netback. We see that rsp_cons is the same value as rsp_prod, with req_prod 236 slots away(tx ring is full). From looking at the netfront driver code, it looks as if xennet_tx_buf_gc processing only happens if rsp_prod is more than rsp_cons. Our

Hi, I ran into an issue where netback driver is crashing with BUG_ON(npo.meta_prod > ARRAY_SIZE(netbk->meta)). It is happening in Intel 10Gbps network when larger mtu values are used. The problem seems to be the way the slots are counted. After applying this patch things ran fine in my environment. I request to validate my changes. Thanks Siva

The xencommons runlevel script has a few modprobe calls to load drivers for dom0. Recently also the backend drivers for vbd and vif were added. Unfortunately without an explanation why that is (suddenly) needed. Now that I have been hitting such missing backend driver issue as well with a xenlinux based dom0 kernel I wonder how to handle the situation. The pvops kernel has 3 backend drivers

This is a cherry pick of two patches that add support for guest paged out frames in the XCP 2.6.32 dom0 patch queue. First patch propagates the ENOENT returned by the hypervisor in the case of a paged out page, all the way up the call chain to the MMAPBATCH_V2 ioctl. The ioctl is mainly used to harvest those return values and retry. The second patch adds retry loops to all backend grant

> http://lists.xensource.com/archives/html/xen-devel/2005-12/msg00238.html > > > > > > The issue is that PG_arch_1 is reserved for arch-specific > > usage, the paravirtualization changes for Xenlinux utilize > > it (to mark foreign pages) because it was otherwise unused > > in Linux/x86. But Xen is no longer an arch. > > > > Grep''ing

The main goal is to create an example to be used as template or guideline for contributors when they wish to create a new virtio device and to document "the right way" to do so. It consists of several parts: 1. The device specification * it can be found in the device header of the implementation * it will hopefully be added to the official virtio specification

This dependence is undesirable and logically incorrect. It''s undesirable because Xen network protocol should not depend on a OS-specific constant. It''s incorrect because the ring slots required doesn''t correspond to the number of frags a SKB has (consider compound page frags). This patch removes this dependence by correctly counting the ring slots required.

A buggy or malicious frontend should not be able to confuse netback. If we spot anything which is not as it should be then shutdown the device and don''t try to continue with the ring in a potentially hostile state. Well behaved and non-hostile frontends will not be penalised. As well as making the existing checks for such errors fatal also add a new check that ensures that there