search for: vif

...| 44 ++++++++++++++++---- 4 files changed, 109 insertions(+), 30 deletions(-) diff --git a/drivers/net/xen-netback/common.h b/drivers/net/xen-netback/common.h index f541ba9..cc2a9f0 100644 --- a/drivers/net/xen-netback/common.h +++ b/drivers/net/xen-netback/common.h @@ -63,8 +63,11 @@ struct xenvif { u8 fe_dev_addr[6]; - /* Physical parameters of the comms window. */ - unsigned int irq; + /* Physical parameters of the comms window. + * When feature-split-event-channels = 0, tx_irq = rx_irq. + */ + unsigned int tx_irq; + unsigned int rx_irq; /* List of frontends t...

...+ 5 files changed, 77 insertions(+), 16 deletions(-) diff --git a/drivers/net/xen-netback/common.h b/drivers/net/xen-netback/common.h index b4a9a3c..55b8dec 100644 --- a/drivers/net/xen-netback/common.h +++ b/drivers/net/xen-netback/common.h @@ -87,9 +87,13 @@ struct pending_tx_info { struct xenvif_rx_meta { int id; int size; + int gso_type; int gso_size; }; +#define GSO_BIT(type) \ + (1 << XEN_NETIF_GSO_TYPE_ ## type) + /* Discriminate from any valid pending_idx value. */ #define INVALID_PENDING_IDX 0xFFFF @@ -150,9 +154,10 @@ struct xenvif { u8 fe_dev_addr...

...3 files changed, 63 insertions(+), 26 deletions(-) diff --git a/drivers/net/xen-netback/common.h b/drivers/net/xen-netback/common.h index 94b79c3..9d7f172 100644 --- a/drivers/net/xen-netback/common.h +++ b/drivers/net/xen-netback/common.h @@ -151,6 +151,9 @@ void xen_netbk_queue_tx_skb(struct xenvif *vif, struct sk_buff *skb); /* Notify xenvif that ring now has space to send an skb to the frontend */ void xenvif_notify_tx_completion(struct xenvif *vif); +/* Prevent the device from generating any further traffic. */ +void xenvif_carrier_off(struct xenvif *vif); + /* Returns number of ring...

...ng VMs. Example: 100Mbits ~ 200kpps using 64B packets. This patch provides a new option to limit VMs maximum packets per second emission rate. It follows the same credits logic used for throughput shaping. For the moment we have considered each "txreq" as a packet. PPS limits is passed to VIF at connection time via xenstore. PPS credit uses the same usecond period used by rate shaping check. known limitations: - by using the same usecond period, PPS shaping depends on throughput shaping. - it is not always true that a "txreq" correspond to a paquet (fragmentation cases) b...

...--- 2 files changed, 24 insertions(+), 29 deletions(-) diff --git a/drivers/net/xen-netback/interface.c b/drivers/net/xen-netback/interface.c index 087d2db..5c10e87 100644 --- a/drivers/net/xen-netback/interface.c +++ b/drivers/net/xen-netback/interface.c @@ -96,18 +96,24 @@ static irqreturn_t xenvif_interrupt(int irq, void *dev_id) static int xenvif_start_xmit(struct sk_buff *skb, struct net_device *dev) { struct xenvif *vif = netdev_priv(dev); + unsigned int ring_slots_required; BUG_ON(skb->dev != dev); if (vif->netbk == NULL) goto drop; + ring_slots_required = xen_netb...

Based on Waldi''s RFC at http://lists.xen.org/archives/html/xen-devel/2012-09/msg00943.html To use it set vif.default.script="vif-openvswitch" in /etc/xen/xl.conf or use script=vif-openvswitch in the vif configuration. Appears to do the right thing for PV and HVM guests (including tap devices) and with stubdomains. In order to support VLAN tagging and trunking the "bridge" specified i...

...t: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > > UEVENT[1133877953] add@/devices/xen-backend/vbd-4-2049 > > UEVENT[1133877953] add@/devices/xen-backend/vif-4-0 > UEVENT[1133877953] > > add@/class/net/vif4.0 UEVENT[1133877953] > > online@/devices/xen-backend/vif-4-0 > > UDEV [1133877956] add@/devices/xen-backend/vbd-4-2049 > > > > Here is the output when the vbd failed: > > > > UEVENT[1133880108] add@/...

...ack.c | 14 +++++++------- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/drivers/net/xen-netback/common.h b/drivers/net/xen-netback/common.h index 5715318..400fea1 100644 --- a/drivers/net/xen-netback/common.h +++ b/drivers/net/xen-netback/common.h @@ -163,6 +163,7 @@ struct xenvif { unsigned long credit_usec; unsigned long remaining_credit; struct timer_list credit_timeout; + u64 credit_window_start; /* Statistics */ unsigned long rx_gso_checksum_fixup; diff --git a/drivers/net/xen-netback/interface.c b/drivers/net/xen-netback/interface.c index 01bb854..45993...

Hi, > Can you manually do on the xen interfaces what the scripts would? How about > doing it on some other interface configured in a similar way? Toying with the vif-route script, I might have found a workaround for this issue. If I disable the ifconfig and ip route commands from vif-route script, and bring up vif interface by hand later on, everything seems to work. In other works, bringing up the interface in vif-route script causes it to stay up when I shut...

# HG changeset patch # User Brendan Cully <brendan@cs.ubc.ca> # Date 1282083158 25200 # Node ID 74b9fe513d8591ca14233590062079b042abb68d # Parent 774dfc178c39bd3fe2ec14b4f96e60b78391b397 hotplug: 21549:8bcaec29574e breaks vif-script with arguments. For example, (vif-script ''vif-bridge bridge=eth1'') in xend-config.sxp will cause vif-setup to attempt to execute ''vif-bridge bridge=eth1'' due to a quoting mismatch. The fix appears to be to remove the extra quotes around "$script&quot...

...ng some problems when I start the DomU. In detail, it means that the DomU IP-Adress will not be implemented in the Kernel routing table after starting the domU via "xm create /<path +configfle>" After making a "netstat -nr" it will not show the IPadress bound to the VIF<..>-interface. A small echo in the vif-route script shows that the variable $IP is empty. So no value will be available, therefore the script can''t work. if [ "${ip}" ] ; then # If we''ve been given a list of IP addresses, then add routes from dom0 to...

....7.13-2 ii ucf 3.0036 ii udev 232-25+deb9u2 ii xenstore-utils 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- Configuration Files: /etc/default/xendomains changed [not included] /etc/xen/scripts/vif-bridge changed [not included] /etc/xen/scripts/vif-common.sh changed [not included] /etc/xen/xend-config.sxp changed [not included] /etc/xen/xl.conf changed [not included] -- no debconf information Hi all I've already filed this issue with the Debian user-list and XEN project - they asked m...

Hi, the vif scripts (vif-route, vif-bridge, etc.) that come with xen just don't work for me. I don't feel like I need a bridged setup. My ISP insists of routing the IPs of the domUs to my dom0. So now I'm using script=vif-route. But it has some caveats ... The vif-route script turns on proxy_arp,...

Package: src:xen Version: 4.17.3+10-g091466ba55-1~deb12u1 Severity: wishlist I wasn't sure if this script comes from Debian or Xen or somewhere else, so I thought it safest to report it here. /etc/xen/scripts/vif-bridge handles MTU settings in the vif, but the otherwise similar /etc/xen/scripts/vif-openvswitch does not. I added it in, here's the diff-c and the full fixed file is also attached. *** vif-openvswitch.orig 2024-03-19 11:53:13.000000000 +0200 --- vif-openvswitch 2024-03-19 11:56...

Hi, I've been generating linear models with lm(). I wanted to look at the VIF's for the coefficient. Using the vif() function from the package Design, I would get unusually high VIF's. However using vif() from the car package I get more reasonable values (ie in line with the quality of the model). What is the difference between the two vif functions? (I dont have a...

Hi, we are trying to secure our Xen boxes with IPtables on Dom0 but we always seem to get cut off and can only cure it be rebooting the box. Has anyone got a sucessful config they can share that secures the server with one nic? We are using Xen 3.0.4 thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew...

hi, I am trying to add xenbus watch support to mini-os, but am getting into a endless loop of watches firing over and over. Below is an excerpt from the xenstore tracefile: IN 0x805acc8 20070103 19:32:18 WATCH (/local/domain/0/backend/vif/26/0/state 00043818 ) CREATE watch 0x805a8b8 OUT 0x805acc8 20070103 19:32:18 WATCH (OK ) OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT (/local/domain/0/backend/vif/26/0/state 00043818 ) IN 0x805acc8 20070103 19:32:18 UNWATCH (/local/domain/0/backend/vif/26/0/state 00043818 ) DESTROY watch 0x805a8b8...

Hello. I''m new to the list and I hope this is not a FAQ. I searched the archives and didn''t find an answer... Quick question : Is there a limitation if the vif code cutting at 1500 bytes ?? I''m trying to implement an IPv6 router/Firewall (2 XenU) Xen 2.0.6, Linux 2.6 is used on xen0 and XenU. The physical machine has 2 interfaces, eth0 (which is connected to an ethernet, non 802.1q port ) and eth1 (which is connected to an ethernet 802.1q port...

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: normal My setup is a basic one. No changes to the /etc/xen/* files. Network in a domU works perfectly fine. But, after shutdowning a domU, I can see the following lines in /var/log/debug: May 6 10:31:45 vaio logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/18/0 May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge: brctl delif xenbr0 vif18.0 failed May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge: ifconfig vif18.0 down failed May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge: Successful vif-br...