From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Dynamic Linux Traffic Control
Date: Mon, 26 Jun 2006 12:53:37 +0000 [thread overview]
Message-ID: <449FD8D1.10501@andyfurniss.entadsl.com> (raw)
In-Reply-To: <e25463520606220231h55256350vc7987fce57a89b82@mail.gmail.com>
Paul wrote:
> Hey all, heres my problem/s.
>
> I have to write code which upon a message from another component
> 1. Reserves bandwidth for a voip call between 2 hosts.My code will
> reside on
> neither of the hosts but the hosts will have to go through me to talk to
> eachother.
>
> 2. Since i'm reserving bandwidth for these hosts to talk to eachother i
> have
> to limit everything else.
>
> 3. I need to do this on-the-fly. i.e > I may recieve a request for several
> calls, i need to remove the traffic control when a call is ended and i need
> to keep limiting all other traffic to give each call its own defined amount
> of bandwidth.
>
> I have being pulling my hair out trying to do the above with tc, so can
> anyone help ? Is tc filters the best solution ? Is there anything else
> thats
> more dynamic ?
As long as you have enough bandwidth for the calls then just setting
htb/hfsc up to give prio/guarantees to voip will reserve the bandwidth
- and let other traffic use it when voip traffic is not present.
If you are shaping ingress from the wrong end of the bottleneck you will
need to sacrifice bandwidth to get control.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-06-26 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 9:31 [LARTC] Dynamic Linux Traffic Control Paul
2006-06-26 12:53 ` Andy Furniss [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=449FD8D1.10501@andyfurniss.entadsl.com \
--to=lists@andyfurniss.entadsl.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.