All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bob Puff@NLE" <bob@nleaudio.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Need big buffer!
Date: Thu, 08 Feb 2007 17:42:36 +0000	[thread overview]
Message-ID: <45CB610C.70905@nleaudio.com> (raw)

Hi gang,

I have an application that is sending streaming media to a server.  The encoder computer sends an
average of 200kbit stream; but for short, 1 second bursts, can hit 400-500kbits.  After it does one
of these bursts, it reduces its output for another second or two, so that it maintains its average
of 200kbits.

The problem is that it is sending UDP packets into a DSL link that has a fixed upstream cap of
300kbit.  All is fine until it decides to burst, then I get dropped packets.

Is there a way I can insert a linux box after the encoding machine that I can use some traffic
shaping to:

1. Make sure it never sends more than 300k up (I do know how to do this now)
2. Make a big buffer so that I can still get all the data through the pipe, albeit with some delay,
when these bursts happen.  I would need this buffer to handle at least 2 seconds worth, maybe more.

I need something like this:

Time    IN       OUT
(secs)  (kbit)   (kbit)
----------------------
0.0	200	200
0.5	200	200
1.0	350	300
1.5	400	300
2.0	25	175
2.5	50	50
3.0	175     175
3.5	200     200
	

...etc...

Ideas?

Bob

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-02-08 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 17:42 Bob Puff@NLE [this message]
2007-02-08 17:46 ` [LARTC] Need big buffer! Larry Brigman
2007-02-09  1:05 ` Bob Puff
2007-02-09  2:31 ` Bob Puff@NLE
2007-02-09 16:00 ` Martin A. Brown

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=45CB610C.70905@nleaudio.com \
    --to=bob@nleaudio.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.