All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 2/9]: Query supported CCIDs
Date: Mon, 01 Oct 2007 11:07:24 +0000	[thread overview]
Message-ID: <200710011207.24964@strip-the-willow> (raw)
In-Reply-To: <200709281630.17307@strip-the-willow>

|  One thing is the pointer in the request_sock case that I have to
|  figure out what is best and possibly rework your patches to provide what
|  I think is best.
|  
I am looking forward to that - if you want me to change single patches, let me know.

I had one more thought regarding timestamping: currently CCID2 uses the old RFC2988 
RTT mechanism from Jacobson's old 1988 paper. RFC 4341 says that the sampling should 
be done at most once per cwnd, but RFC 1323 says that this is insufficient for 
high-speed networking. And today it is almost impossible to buy a computer /not/ with
a Gbps ethernet card.

In short - if you change the architecture, is is possible to keep a door open to
add a timestamping-based RTT algorithm to CCID2? That has been your suggestion 
anyway some emails ago and I like the idea.

There is further stuff that can be shared - I have some ideas for using the ICSK_RETRANS
to replace a lot of code duplication for the RTO timer in CCID2. Would make sense, since
in OPEN/PARTOPEN state the retransmit timer is never used (only for Request/Close/CloseReq).

  parent reply	other threads:[~2007-10-01 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 15:30 [PATCH 2/9]: Query supported CCIDs Gerrit Renker
2007-09-28 18:21 ` Arnaldo Carvalho de Melo
2007-09-29 16:24 ` Gerrit Renker
2007-09-29 17:58 ` Arnaldo Carvalho de Melo
2007-10-01 11:07 ` Gerrit Renker [this message]
2007-10-01 18:26 ` Ian McDonald

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=200710011207.24964@strip-the-willow \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=dccp@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.