From: Rodolfo Brasnarof <rodob@datafull.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TC not working well with bonded nics please help
Date: Tue, 20 Mar 2007 03:41:23 +0000 [thread overview]
Message-ID: <20070320004123.19b3a7d3@localhost> (raw)
In-Reply-To: <3742.65.115.68.194.1174346513.squirrel@webmail.calsoftinc.com>
On Tue, 20 Mar 2007 04:51:53 +0530 (IST)
dhananjay.tembe@calsoftinc.com wrote:
>
> Hi,
> I am facing a problem when I run tc on the bonded nic cards.
> When I run tc on a single nic card, it worked perfectly fine. But
> when I run tc on a bond of two nics, tc gives poor performance. The
> two nics were bonded in round-robin (load balancing) mode. I created
> a qdisc, class and a filter as follows:
>
> tc qdisc add dev bond0 root handle 1: htb
> tc class add dev bond0 parent 1: classid 1:1 htb rate 240mbps
> tc class add dev bond0 parent 1:1 classid 1:2 htb rate 50 ceil 50
> quantum 1500
>
> I started a TCP traffic between this bond (2gbit bandwidth) and a
> remote nic (1gbit bandwidth).
> Without qos, bond was transmitting at 960Mbps.
> After I executed above mentioned commands, it was expected that the
> bond will transmit at 400Mbps but it was transmitting only at 70Mbps.
> Same thing was observed with different qos rates for class 1:2,
> outbound traffic through bond was very less than the rate specified
> in the tc command.
>
> Is getting poor performance after running tc over a bond is a known
> issue? Please help me with this issue.
Perhaps you can use an IMQ device for traffic control/shaping.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-03-20 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 23:33 [LARTC] TC not working well with bonded nics please help dhananjay.tembe
2007-03-20 3:41 ` Rodolfo Brasnarof [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070320004123.19b3a7d3@localhost \
--to=rodob@datafull.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.