From: jzeeff@internet2.edu
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Split bandwidth equally per IP
Date: Sun, 07 Dec 2003 00:12:02 +0000 [thread overview]
Message-ID: <marc-lartc-107075776620012@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107056586923918@msgid-missing>
ESFQ allows this to be "per ip address", which solves the problem.
I have not seen applications that grab many ip addresses for a single host,
although this is possible.
Quoting Mihai Vlad <mihaivlad@web-profile.net>:
> Hello Martin,
>
> I have recently read your howto from:
> http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Traffi
> c-Control-HOWTO.html
>
> I quote:
>
> "Of the many types of contention for network bandwidth, this is one of the
> easier types of contention to address in general. By using the SFQ qdisc,
> traffic in a particular queue can be separated into flows, each of which
> will be serviced fairly (inside that queue). Well-behaved applications (and
> users) will find that using SFQ and ESFQ are sufficient for most sharing
> needs.
>
> The Achilles heel of these fair queuing algorithms is a misbehaving user or
> application which opens many connections simultaneously (e.g., eMule,
> eDonkey, Kazaa). By creating a large number of individual flows, the
> application can dominate slots in the fair queuing algorithm. Restated, the
> fair queuing algorithm has no idea that a single application is generating
> the majority of the flows, and cannot penalize the user. Other methods are
> called for."
>
>
>
>
>
>
>
> Can you post a real script using esfq, that splits the bandwidth equally
> per
> IP?
>
> The documentation on esfq is scarce and I have no idea where to start from.
>
> Thanks again for your time.
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Martin A. Brown [mailto:mabrown-lartc@securepipe.com]
> Sent: Friday, December 05, 2003 7:03 PM
> To: Mihai Vlad
> Cc: lartc@mailman.ds9a.nl
> Subject: RE: [LARTC] Split bandwidth equally per IP
>
> Achtung! There is already an esfq qdisc [0] which does this! This patch
> may be a good one, but since esfq already exists, perhaps you could try
> that instead.
>
> -Martin
>
> [0] http://www.ssi.bg/~alex/esfq/index.html
>
> --
> Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-07 0:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 18:52 [LARTC] Split bandwidth equally per IP Mihai Vlad
2003-12-04 19:44 ` Stef Coene
2003-12-05 15:08 ` jzeeff
2003-12-05 15:19 ` jzeeff
2003-12-05 15:57 ` Mihai Vlad
2003-12-05 17:02 ` Martin A. Brown
2003-12-05 17:50 ` jzeeff
2003-12-05 22:45 ` Mihai Vlad
2003-12-07 0:12 ` jzeeff [this message]
2003-12-07 6:21 ` 'Martin A. Brown'
2003-12-07 6:23 ` 'Martin A. Brown'
2003-12-07 8:30 ` Mihai Vlad
2003-12-07 9:32 ` Chijioke Kalu
2003-12-07 21:19 ` Nickola Kolev
2003-12-17 16:56 ` Mihai Vlad
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=marc-lartc-107075776620012@msgid-missing \
--to=jzeeff@internet2.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox