netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eddie Kohler <kohler@cs.ucla.edu>
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>,
	Leandro Sales <leandroal@gmail.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	ian.mcdonald@jandi.co.nz, DCCP Mailing List <dccp@vger.kernel.o
Subject: Re: [RFC] dccp ccid-3: High-res or low-res timers?
Date: Mon, 17 Nov 2008 11:27:29 -0800	[thread overview]
Message-ID: <4921C5A1.5030609@cs.ucla.edu> (raw)
In-Reply-To: <20081115105042.GA7798@gerrit.erg.abdn.ac.uk>

Gerrit Renker wrote:
> I would appreciate some advice and insights regarding the use of
> high-resolution timers within a transport protocol, specifically
> DCCP with CCID-3 (RFC 5348).
> 
 > ...
 >
> Summing up, I have doubts that basing CCID-3 will bring advantages and
> would much rather go the other way and (consistently) use lower resolution.
> 
> Thoughts?

I agree.  If one way must be chosen, then choose lower resolution timers.

The biggest potential problem with lower-resolution timers is that a sender's 
rate might be limited, not by network characteristics, but by timer 
resolution.  But DCCP allows a fair amount of burstiness already.  And there 
may be ways to avoid rate limitation in common cases without resorting to 
hrtimers.  For example, a sending application could use a mixture of 
non-blocking system calls, allowing the sending application to "poke" the DCCP 
implementation on every scheduling.

At any rate, it seems worth trying.

Eddie


  parent reply	other threads:[~2008-11-17 19:35 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 [this message]
     [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

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=4921C5A1.5030609@cs.ucla.edu \
    --to=kohler@cs.ucla.edu \
    --cc=acme@redhat.com \
    --cc=dccp@vger.kernel.o \
    --cc=gerrit@erg.abdn.ac.uk \
    --cc=ian.mcdonald@jandi.co.nz \
    --cc=leandroal@gmail.com \
    /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).