WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Traffic Shaping: Ingress qdisc not working in Dom0 (3.0.

To: Timo Benk <timo.benk@xxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Traffic Shaping: Ingress qdisc not working in Dom0 (3.0.4-1)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 04 Feb 2007 14:53:24 +0000
Cc: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 04 Feb 2007 06:53:03 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45C5E08B.3090202@xxxxxx>
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: AcdIbDg0dvbT0bRfEduJNQAX8io7RQ==
Thread-topic: [Xen-devel] Traffic Shaping: Ingress qdisc not working in Dom0 (3.0.4-1)
User-agent: Microsoft-Entourage/11.2.5.060620
On 4/2/07 13:32, "Timo Benk" <timo.benk@xxxxxx> wrote:

> The ingress qdisc on peth0 gets no traffic somehow.
> 
> If i stop the bridge via 'network-bridge stop', the ingress qdisc
> works as expected. But as far as the bridge is created, the
> ingress qdisc stops working on peth0.

My guess would be that this is unlikely to be a Xen-specific issue, and that
something has changed in packet delivery that causes packets picked up by a
bridge to not be checked for ingress filtering. This is fairly plausible
because bridged packets are stolen from the normal packet-reception path
quite early on, and it's very believable that changes in that area of the
code wouldn't have been tested for tc/etherbridge interactions. I've cc'ed
Herbert Xu just in case he has any ideas, since he's often aware of goings
on in the Linux networking code.

 -- Keir



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

<Prev in Thread] Current Thread [Next in Thread>