From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey Talikov Date: Wed, 05 Jun 2002 12:03:18 +0000 Subject: Re: [LARTC] Bandwidth allocation by IP Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Thanks for your note about my error !! You right needed dst ip but I write src :(( 05.06.2002 16:53:29, Alexander Atanasov wrote: > Hi there! > >On Wed, 05 Jun 2002 16:19:41 +0500 >"Alexey Talikov" wrote: > >> I rename files gzip its and attach to this mail but don't change >> anything patch kernel and tc > > I'll put them somewhere on the web tonight and provide an url. > >> Note it give you equal division for a long term not at the moment >> Example: >> >> tc qdisc add dev eth1 root handle 1:0 esfq hash src >> >> It make equal priority for session based on ip address not tcp session >> like classic SFQ For detail see SFQ > > Note that sfq is on egress and client IPs are destinations, not sources, >so you should use dst hash to divide bandwidth between clients, if you use src hash you have equal priority on server flows not on clients ones: client A downloads from server X and from server Y, client B downloads from server Z - you have bandwidth devided to X:Y:Z, not A:B, since downloads are coming from X/Y/Z(source) to A/B(destination). > >-- >have fun, >alex >P.S. Thank you for the feedback and trying it. :) > ----------------------------------- mailto:alexey_talikov@texlab.com.uz BR Alexey Talikov FORTEK ----------------------------------- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/