All of lore.kernel.org
 help / color / mirror / Atom feed
From: Satoru SATOH <satoru.satoh@gmail.com>
To: Ryousei Takano <ryousei@gmail.com>
Cc: Ivan Novick <novickivan@gmail.com>, netdev@vger.kernel.org
Subject: Re: 200 millisecond timeouts in TCP
Date: Sat, 5 Jun 2010 00:02:02 +0900	[thread overview]
Message-ID: <20100604150202.GA8268@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilsYS8P2VqATmasXjjdhjPMMZznIHBByXc1i8cU@mail.gmail.com>

It's possible to tune the RTO min value (rto_min) per route since
2.6.23+.  (see also the manual of iproute2, ip(8) )

- satoru

On Fri, Jun 04, 2010 at 03:58:57PM +0900, Ryousei Takano wrote:
> On Fri, Jun 4, 2010 at 7:37 AM, Ivan Novick <novickivan@gmail.com> wrote:
> > Hello,
> >
> > Using tcpdump and systemtap I am seeing that sometimes retransmission
> > of data is sent after waiting 200 milliseconds.  However sometimes
> > retransmissions happen quicker.
> >
> > Is there a specifc event that causes these 200 milisec delays to kick
> > in?  Are those events identifiable in netstat -s output?
> >
> > Also do you know if the timeout numbers for TCP are configurable parameters?
> >
> The minimum RTO value is fixed to 200 ms.  It is useful to make the min/max
> RTO values tunable.  For example, reducing the minimum RTO value is effective
> for TCP incast problem [1].  Of course, it may occur spurious retransmissions.
> 
> [1] Vijay Vasudevan, et al, Safe and Effective Fine-grained TCP Retransmissions
> for Datacenter Communication, SIGCOMM2009
> 
> In Solaris, there are two tunable parameters: tcp_rexmit_interval_min/max.
> 
> Do you have plan to introduce sysctl parameters like these to the Linux.
> 
> Thanks,
> Ryousei

  reply	other threads:[~2010-06-04 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 22:37 200 millisecond timeouts in TCP Ivan Novick
2010-06-03 22:51 ` Mitchell Erblich
2010-06-03 23:10 ` Hagen Paul Pfeifer
2010-06-04  0:05   ` Ivan Novick
2010-06-04  0:11   ` Ivan Novick
2010-06-04  0:45     ` Hagen Paul Pfeifer
2010-06-04  1:13   ` Mitchell Erblich
2010-06-04  6:58 ` Ryousei Takano
2010-06-04 15:02   ` Satoru SATOH [this message]
2010-06-04 22:55     ` Ryousei Takano

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=20100604150202.GA8268@localhost.localdomain \
    --to=satoru.satoh@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=novickivan@gmail.com \
    --cc=ryousei@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 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.