RE: [Xen-devel] [PATCH] MAC Matching vif-route & tip

To:	"Andy Lee" <andylee@xxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] [PATCH] MAC Matching vif-route & tip
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Wed, 7 Sep 2005 18:44:27 +0100
Delivery-date:	Wed, 07 Sep 2005 17:42:23 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcWz0Hzn/NfqgXpcRkW5URqE3f3uYwAAwx3A
Thread-topic:	[Xen-devel] [PATCH] MAC Matching vif-route & tip

> This patch will setup iptable rules for vif's that does MAC 
> matching, as PHYSDEV matching only works for bridged devices. 

Is that definitely the case? I don't see why physdev shouldn't work with
routed setups.

> On a separate but still networking issue, I noticed that my 
> XenU's outbound traffic is sporadic (between 800KB/sec and 
> 2MB/sec).  The problem is the default qdisc being inadequate. 
>  So I fix it with:
> 
> XenU# tc qdisc add dev eth0 root tbf rate 50mbit latency 20ms 
> burst 50k

How much more buffering does this add?

Thanks,
Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

RE: [Xen-devel] [PATCH] MAC Matching vif-route & tip