From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to guarantee 1/numflows bandwidth to each
Date: Wed, 11 May 2005 03:35:37 +0000 [thread overview]
Message-ID: <42817D89.DDF0F771@iswest.com> (raw)
In-Reply-To: <20050509181700.GA32621@vaxerdec.bmt.questra.com>
Scott Mcdermott wrote:
>
> I am looking for a simple way to guarantee to each flow
> going through my traffic control point 1/numflows of
> bandwidth. I thought using SFQ would do this effectively
> but it appears to be quite unfair: a very high speed
> download that fills the pipe easily starves smaller flows to
> the point where it becomes unusable (especially if they are
> at all interactive)
>
> Because numflows is dynamic, I'm not sure how I would have
> the bandwidth allocated to each flow change dynamically and
> automatically as flows are added and removed.
>
> Anyone have an idea how to implement this? Thanks.
Perhaps you should look at esfq rather than sfq. esfq lets you specify
quantum in bytes, depth in flows, limit in packets, and a source or dest
hash. Don't apply any sfq to what Wondershaper calls "interactive".
You need to match esfq to the kernel version; 2.6 uses a different esfq
than 2.4.
--
buck
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-05-11 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 18:17 [LARTC] how to guarantee 1/numflows bandwidth to each flow Scott Mcdermott
2005-05-10 18:42 ` Krystian Antoni
2005-05-11 3:35 ` gypsy [this message]
2005-05-11 22:53 ` [LARTC] how to guarantee 1/numflows bandwidth to each Andy Furniss
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=42817D89.DDF0F771@iswest.com \
--to=gypsy@iswest.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.