On Wed, 2011-03-02 at 22:18 +0100, Daniel Lezcano wrote: > On 02/28/2011 11:20 AM, Farcasi Ana-Maria wrote: > > Hi, > > > > Indeed, we were refering to the network bandwidth limitation. Sorry for the > > confusion. > > > > We have already done some tests with this limitation using tc and cgroups > > and we have reached the conclusion that the classification is done > > correctly, but the limitation of the bandwidth is not done at all. Here we > > have attached our results [1]. > > I just noticed Andre added the network bandwidth limitations from > outside of the container using the side of the pair device veth on the host. > > http://andre.people.digirati.com.br/lxc-create.sh
I'm not sure about what the context is here :) I did it that way because I couldn't get it to work with tc and cgroups. The downside of my approach is one extra iptables rule to mark the packets and one "tc filter" rule per container, if you want to have individual bandwidth limiting. Andre ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
