All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gavin McCullagh <Gavin.McCullagh@nuim.ie>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH/RFC] [v2] TCP: use non-delayed ACK for congestion	control RTT
Date: Wed, 19 Dec 2007 11:31:25 +0000	[thread overview]
Message-ID: <20071219113125.GF31508@nuim.ie> (raw)
In-Reply-To: <Pine.LNX.4.64.0712191241450.11908@kivilampi-30.cs.helsinki.fi>

Hi,

On Wed, 19 Dec 2007, Ilpo Järvinen wrote:

> Isn't it also much better this way in a case where ACK losses happened,
> taking the longest RTT in that case is clearly questionable as it
> may over-estimate considerably.

Quite so.

> However, another thing to consider is the possibility of this value being 
> used in "timeout-like" fashion in ca modules (I haven't read enough ca 
> modules code to know if any of them does that), on contrary to 
> determinating just rtt or packet's delay in which case this change seems 
> appropriate (most modules do the latter). 

I'm not aware of any, but I haven't read them all either.  I would have
thought tp->srtt was the value to use in this instance, but perhaps the
individual timestamps including delack delay are useful.

> Therefore, if timeout-like module exists one should also add
> TCP_CONG_RTT_STAMP_LONGEST for that particular module and keep using
> seq_rtt for it like previously and use ca_seq_rtt only for others.

Seems reasonable.  I'll add this.

> This part doesn't exists anymore in development tree. Please base this 
> patch (and anything in future) you intend to get included to mainline
> onto net-2.6.25 unless there's a very good reason to not do so or 
> whatever 2.6.xx is the correct net development tree at that time (if
> one exists). Thanks.

Will do.   I gather I should use the latest net- tree in future when
submitting patches.

Thanks for the helpful comments,

Gavin


  reply	other threads:[~2007-12-19 11:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 13:44 [PATCH/RFC] TCP: use non-delayed ACK for congestion control RTT Gavin McCullagh
2007-12-18 20:40 ` [PATCH/RFC] [v2] " Gavin McCullagh
2007-12-19 10:28   ` Gavin McCullagh
2007-12-19 11:08   ` Ilpo Järvinen
2007-12-19 11:31     ` Gavin McCullagh [this message]
2007-12-19 13:30       ` Ilpo Järvinen
2007-12-21 11:14         ` David Miller
2007-12-21 13:31           ` Gavin McCullagh
2007-12-21 14:05             ` David Miller
2007-12-21 14:07             ` Ilpo Järvinen
2007-12-21 14:10               ` Ilpo Järvinen
2007-12-30  1:15               ` [PATCH/RFC] [v3] " Gavin McCullagh
2007-12-30  1:25                 ` Gavin McCullagh
2007-12-30  3:09                   ` David Miller
2007-12-30 12:20                     ` Gavin McCullagh
2007-12-30  3:06                 ` David Miller
2007-12-30  9:43                 ` Ilpo Järvinen
2007-12-30 12:35                   ` Gavin McCullagh

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=20071219113125.GF31508@nuim.ie \
    --to=gavin.mccullagh@nuim.ie \
    --cc=ilpo.jarvinen@helsinki.fi \
    --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 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.