netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: Ian McDonald <ian.mcdonald@jandi.co.nz>
Cc: Leandro Sales <leandroal@gmail.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	DCCP Mailing List <dccp@vger.kernel.org>,
	netdev@vger.kernel.org, DCCP mailing list <dccp@ietf.org>
Subject: Re: [RFC] dccp ccid-3: High-res or low-res timers?
Date: Thu, 20 Nov 2008 07:24:08 +0100	[thread overview]
Message-ID: <20081120062408.GD6227@gerrit.erg.abdn.ac.uk> (raw)
In-Reply-To: <5640c7e00811180941l671fd3a0w390529df9222163e@mail.gmail.com>

Thanks Ian for the comments and suggestions, which is input for further
work. Hope to start this poco a poco soon.

| > Do you think we could live with clamping the RTT to some sensible
| > minimum, since on a local LAN the use of congestion control is
| > questionable? I was thinking in the order of 0.5 ... 1msec.
| >
| I think that is a good idea - if 1 msec, and HZ = 1000 then we
| wouldn't lose any transmission capability.
| 
Probably it will require a bit of testing, it might be that some
fine-tuning is needed since a lower RTT also means a lower maximum
throughput -- but maybe that limit is fully sufficient for the target
operational range of CCID-3 (streaming, not bulk data transfer).

Gerrit

      reply	other threads:[~2008-11-20  6:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5bc4c4570810171021ua6371ebs1ffdf471382a8b13@mail.gmail.com>
     [not found] ` <20081105052733.GG6564@gerrit.erg.abdn.ac.uk>
     [not found]   ` <5bc4c4570811060538h2d662507u5de1fb62c61cd569@mail.gmail.com>
     [not found]     ` <20081106152048.GA3621@gerrit.erg.abdn.ac.uk>
     [not found]       ` <20081106153824.GA9709@ghostprotocols.net>
     [not found]         ` <5bc4c4570811060946j4d5d8d1mf88f8b92c72b59c7@mail.gmail.com>
     [not found]           ` <5bc4c4570811061004nfc2afdcn6035d49ae654aef1@mail.gmail.com>
     [not found]             ` <5bc4c4570811061017j3acef860vee84992e7295d06d@mail.gmail.com>
     [not found]               ` <5bc4c4570811061405qe72e43cx861c537885804132@mail.gmail.com>
     [not found]                 ` <20081108085035.GA7112@gerrit.erg.abdn.ac.uk>
2008-11-15 10:50                   ` [RFC] dccp ccid-3: High-res or low-res timers? Gerrit Renker
2008-11-16  8:14                     ` Ian McDonald
2008-11-17  6:48                     ` David Miller
2008-11-18  5:07                       ` Gerrit Renker
2008-11-17 19:27                     ` Eddie Kohler
     [not found]                     ` <5640c7e00811160014p17414c54v2499c5b1e996278f@mail.gmail.com>
2008-11-17 21:16                       ` [RFC] dccp ccid-3: High-res or low-res timers? <cross post> Gorry Fairhurst
2008-11-18  6:14                       ` [RFC] dccp ccid-3: High-res or low-res timers? Gerrit Renker
2008-11-18 17:41                         ` Ian McDonald
2008-11-20  6:24                           ` Gerrit Renker [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=20081120062408.GD6227@gerrit.erg.abdn.ac.uk \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=acme@redhat.com \
    --cc=dccp@ietf.org \
    --cc=dccp@vger.kernel.org \
    --cc=ian.mcdonald@jandi.co.nz \
    --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).