netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: David Miller <davem@davemloft.net>
Cc: opurdila@ixiacom.com, Netdev <netdev@vger.kernel.org>
Subject: Re: initial congestion window for connections in the listen queue
Date: Tue, 14 Apr 2009 00:54:40 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0904140051100.9234@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <20090413.142653.267913010.davem@davemloft.net>

On Mon, 13 Apr 2009, David Miller wrote:

> From: Octavian Purdila <opurdila@ixiacom.com>
> Date: Mon, 13 Apr 2009 23:46:15 +0300
> 
> > 
> > A question for the TCP wizards:
> > 
> >>struct sock *tcp_create_openreq_child(struct sock *sk, 
> >>        struct request_sock >*req, struct sk_buff *skb)
> >>{
> >>...
> >>         /* So many TCP implementations out there (incorrectly) count the
> >>          * initial SYN frame in their delayed-ACK and congestion control
> >>          * algorithms that we must have the following bandaid to talk 
> >>          * efficiently to them.  -DaveM
> >>          */
> >>          newtp->snd_cwnd = 2;
> > 
> > Shouldn't the same logic from tcp_init_cwnd() be used here?
> > 
> >>From my traces, this seems to prevent TSO from helping short lived 
> > connections.
> 
> On any standard ethernet MTU or larger, you should be getting
> an initial CWND of 3 or 4 because of the logic in tcp_init_cwnd().
> 
> Don't just guesstimate what initial ->snd_cwnd value the
> kernel is using by looking casually at tcpdump traces.  Add
> some kernel debugging printk's and find out for sure.

A long-standing feature in tcp_init_metrics() is such that any of its goto 
reset prevents call to tcp_init_cwnd(). I never remembered to fix that.

-- 
 i.

  reply	other threads:[~2009-04-13 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 20:46 initial congestion window for connections in the listen queue Octavian Purdila
2009-04-13 21:26 ` David Miller
2009-04-13 21:54   ` Ilpo Järvinen [this message]
2009-04-13 21:58     ` David Miller
2009-04-14  8:37       ` Ilpo Järvinen
2009-04-14  9:09         ` David Miller
2009-04-14 13:48         ` Octavian Purdila

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=Pine.LNX.4.64.0904140051100.9234@wrl-59.cs.helsinki.fi \
    --to=ilpo.jarvinen@helsinki.fi \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=opurdila@ixiacom.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).