From: dirk <tigger@lipsia.de>
To: lartc@vger.kernel.org
Subject: [LARTC] How dynamic is tc or my own tc-script?
Date: Fri, 21 Sep 2007 11:41:28 +0000 [thread overview]
Message-ID: <46F3ADE8.9070009@lipsia.de> (raw)
hello,
I would like implement an academic theory of TCP traffic control gateway
for wireless multihop environments. The main part is an dynamic pacing
witch suffers from the RTT and hops in the wireless domain. With
shell-scripts or how ever I can get my information for the actually
pacing-time for an TCP-stream - the time can be chance over established
TCP-session - so it's be a variable*.
How can I implement these pacing-time relatively simple in tc?
My fear I must write a complete new algorithm or so and I can't do this
with a simple script but also written in C. Exists API-functions? Where
can I find a hint or document how can I get my own tc "function"?
* I mean, for example - but I'm rather unconvincing that it's work:
tc add qdisc ...
handle 10: tbf rate ${value} ... # ${value} increase or
decrease over a TCP-session
thanks
Dirk
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2007-09-21 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46F3ADE8.9070009@lipsia.de \
--to=tigger@lipsia.de \
--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.