netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: opurdila@ixiacom.com
Cc: netdev@vger.kernel.org
Subject: Re: initial congestion window for connections in the listen queue
Date: Mon, 13 Apr 2009 14:26:53 -0700 (PDT)	[thread overview]
Message-ID: <20090413.142653.267913010.davem@davemloft.net> (raw)
In-Reply-To: <200904132346.15783.opurdila@ixiacom.com>

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.

  reply	other threads:[~2009-04-13 21:27 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 [this message]
2009-04-13 21:54   ` Ilpo Järvinen
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=20090413.142653.267913010.davem@davemloft.net \
    --to=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).