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/
Home Products Support Community News


Re: [Xen-devel] proposal of xt_physdev's patch to limit traffic

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] proposal of xt_physdev's patch to limit traffic
From: Felix Kuperjans <felix@xxxxxxxxxxxxxxxxxx>
Date: Thu, 21 Oct 2010 14:38:25 +0200
Delivery-date: Thu, 21 Oct 2010 05:39:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BAY156-w293B0735AC6EC055FE54419E5D0@xxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BAY156-w293B0735AC6EC055FE54419E5D0@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100909 Lanikai/3.1.3
I think you don't even need any new netfilter patches or features.

Just using "physdev" together with the "quota" match should be sufficient (maybe it's not in the 2.6.18 kernel, but definitely in recent or pv_ops kernels).

In addition, I don't think that the netfilter will be interested in a quota patch to physdev; physdev is meant to match the device a packages was coming from on a bridge - quotas are definitely the job of the quota match or QoS, not the physdev match.


Am 21.10.2010 12:27, schrieb ahmed amamou:
Good morning every Body

I'm new in modules programming and I've made a patch to limit packet traffic in bridge(patch is joined with the mail).

In order to limit the traffic, i used the netback limitation method to count traffic with skb->len  for each vif to stop traffic, as i can't put down vif, i change the hotdrop flag to 1 (change was based on xt_physdev of dom 0 so  in the patch will find it 1 but it's easy to change the patch to recent dom 0 version by just changing  *hotdrop=1; to *par->hotdrop=true;)

The problem that i have is that when i reach traffic limit (30mb/s by defaut and can be changed via proc EX: "echo vif1.0 312500,50000' >/proc/changeRXrate know that doing it via proc is the worst way but i don't know any other way to do it any suggestion will be welcome ) and begin drop traffic fell terribly and became 10mb/s

will be really thankful if anybody could help me with suggestions and advices in order to  solve this problem



_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>