netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org, netdev@vger.kernel.org,
	Ivo Calado <ivocalado@embedded.ufcg.edu.br>,
	Leandro <leandroal@gmail.com>
Cc: ldecicco.gmail.com@gerrit.erg.abdn.ac.uk
Subject: [RFD] dccp: Rate Mismatch Controller -- still requires high-res timers?
Date: Mon, 9 Aug 2010 12:54:55 +0200	[thread overview]
Message-ID: <20100809105454.GA3591@gerrit.erg.abdn.ac.uk> (raw)

I have finished a simple proof-of-concept implementation of the Rate Mismatch Controller for TFRC and put the patches/results on
  
  http://www.erg.abdn.ac.uk/users/gerrit/dccp/notes/ccid3/sender_notes/rate_mismatch_controller/

The results are not as good as had been hoped - in particular, it still seems
necessary to use high-res timers in order to achieve reasonable stability and
accuracy.

Perhaps I have missed something, but as it stands, I can not see an advantage
in using this for TFRC - comments welcome.

Gerrit

                 reply	other threads:[~2010-08-09 10:58 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=20100809105454.GA3591@gerrit.erg.abdn.ac.uk \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=dccp@vger.kernel.org \
    --cc=ivocalado@embedded.ufcg.edu.br \
    --cc=ldecicco.gmail.com@gerrit.erg.abdn.ac.uk \
    --cc=leandroal@gmail.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).