All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: tsuna <tsunanet@gmail.com>
Cc: "H.K. Jerry Chu" <hkjerry.chu@gmail.com>,
	David Miller <davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
	<pekkas@netcore.fi>, <jmorris@namei.org>,
	<yoshfuji@linux-ipv6.org>, <kaber@trash.net>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tcp: Expose the initial RTO via a new sysctl.
Date: Tue, 31 May 2011 17:25:22 +0200	[thread overview]
Message-ID: <da8dbb76f0cb3762227d8d0a99eaff21@localhost> (raw)
In-Reply-To: <BANLkTimqtjskX5q2ovTp_c05MdqBDOWsRg@mail.gmail.com>


On Tue, 31 May 2011 07:48:09 -0700, tsuna <tsunanet@gmail.com> wrote:

> I talked to Jerry and he's agreed to share some patches that Google
> has been using internally for years.

Great!

> Personally what I think would be ideal would be:
>   1. A sysctl knob for initRTO, to allow people to adjust this
> appropriately for their environment.
>   2. Apply the srtt / rttvar seen on previous connections to new
>   connections.
> 
> Does that sound reasonable?
> 
> For 2), I'm not sure how the details would work yet, I believe the
> kernel already has what's necessary to remember these things on a per
> peer basis, but it would be nice if I could specify things like "for
> 10.x.0.0/16 (local datacenter) use this aggressive setting, for
> 10.0.0.0/8 (my internal backend network) use that, for everything else
> (Internets etc.) use the default".

Skip sysctl, it is deprecated. The initRTO is the ideal candidate for a
per route knob. And happily you will solve 2) with the per route thing too!
;-)

Search the web, you will find some patches where you can see how to extend
the per route system - including iproute2.

Hagen
   

WARNING: multiple messages have this Message-ID (diff)
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: tsuna <tsunanet@gmail.com>
Cc: "H.K. Jerry Chu" <hkjerry.chu@gmail.com>,
	David Miller <davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
	<pekkas@netcore.fi>, <jmorris@namei.org>,
	<yoshfuji@linux-ipv6.org>, <kaber@trash.net>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tcp: Expose the initial RTO via a new sysctl.
Date: Tue, 31 May 2011 17:25:22 +0200	[thread overview]
Message-ID: <da8dbb76f0cb3762227d8d0a99eaff21@localhost> (raw)
In-Reply-To: <BANLkTimqtjskX5q2ovTp_c05MdqBDOWsRg@mail.gmail.com>


On Tue, 31 May 2011 07:48:09 -0700, tsuna <tsunanet@gmail.com> wrote:



> I talked to Jerry and he's agreed to share some patches that Google

> has been using internally for years.



Great!



> Personally what I think would be ideal would be:

>   1. A sysctl knob for initRTO, to allow people to adjust this

> appropriately for their environment.

>   2. Apply the srtt / rttvar seen on previous connections to new

>   connections.

> 

> Does that sound reasonable?

> 

> For 2), I'm not sure how the details would work yet, I believe the

> kernel already has what's necessary to remember these things on a per

> peer basis, but it would be nice if I could specify things like "for

> 10.x.0.0/16 (local datacenter) use this aggressive setting, for

> 10.0.0.0/8 (my internal backend network) use that, for everything else

> (Internets etc.) use the default".



Skip sysctl, it is deprecated. The initRTO is the ideal candidate for a

per route knob. And happily you will solve 2) with the per route thing too!

;-)



Search the web, you will find some patches where you can see how to extend

the per route system - including iproute2.



Hagen

   

  reply	other threads:[~2011-05-31 15:25 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17  7:40 [PATCH] tcp: Expose the initial RTO via a new sysctl Benoit Sigoure
2011-05-17  7:40 ` Benoit Sigoure
2011-05-17  8:01   ` Alexander Zimmermann
2011-05-17  8:34     ` Eric Dumazet
2011-05-17  8:07   ` Eric Dumazet
2011-05-17 11:02     ` Hagen Paul Pfeifer
2011-05-17 11:02       ` Hagen Paul Pfeifer
2011-05-17 12:20       ` Eric Dumazet
2011-05-18 10:43     ` Benoit Sigoure
2011-05-18 19:26       ` David Miller
2011-05-18 19:40         ` tsuna
2011-05-18 19:52           ` David Miller
2011-05-18 20:20             ` Hagen Paul Pfeifer
2011-05-18 20:23               ` David Miller
2011-05-18 20:27                 ` Hagen Paul Pfeifer
2011-05-20 10:27               ` H.K. Jerry Chu
2011-05-20 11:00                 ` Hagen Paul Pfeifer
2011-05-20 11:00                   ` Hagen Paul Pfeifer
2011-05-20 12:37                   ` Alan Cox
2011-05-21  0:06                   ` H.K. Jerry Chu
2011-05-31 14:48                     ` tsuna
2011-05-31 15:25                       ` Hagen Paul Pfeifer [this message]
2011-05-31 15:25                         ` Hagen Paul Pfeifer
2011-05-31 15:28                         ` tsuna
2011-05-31 15:43                           ` Hagen Paul Pfeifer
2011-05-31 15:43                             ` Hagen Paul Pfeifer
2011-05-19  2:22             ` [PATCH] tcp: Implement a two-level initial RTO as per draft RFC 2988bis-02 Benoit Sigoure
2011-05-19  2:22               ` Benoit Sigoure
2011-05-19  2:36               ` David Miller
2011-05-19  3:56                 ` tsuna
2011-05-19  4:14                   ` David Miller
2011-05-19  4:33                     ` tsuna
2011-05-19  5:46                       ` David Miller
2011-05-19  6:36                         ` [PATCH] tcp: Lower the initial RTO to 1s " Benoit Sigoure
2011-05-19  6:36                           ` Benoit Sigoure
2011-05-19 17:42                           ` Yuchung Cheng
2011-05-19  6:47                         ` Benoit Sigoure
2011-05-19  6:47                           ` Benoit Sigoure
2011-05-19 20:16                           ` David Miller
2011-05-19  6:10                       ` [PATCH] tcp: Implement a two-level initial RTO " Alexander Zimmermann
2011-05-19  6:25                         ` tsuna
2011-05-19  6:36                           ` Alexander Zimmermann
2011-05-19  6:42                             ` tsuna
2011-05-19  6:52                               ` Alexander Zimmermann
2011-05-19  7:07                                 ` tsuna
2011-05-19  8:02                                 ` Hagen Paul Pfeifer
2011-05-19  8:02                                   ` Hagen Paul Pfeifer
2011-05-19 16:40                                   ` tsuna
2011-05-19 16:55                                     ` Alexander Zimmermann
2011-05-19 17:11                                       ` tsuna
2011-05-19 19:27                                         ` David Miller
2011-05-19 20:30                                           ` tsuna
2011-05-20  2:01           ` [PATCH] tcp: Expose the initial RTO via a new sysctl H.K. Jerry Chu

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=da8dbb76f0cb3762227d8d0a99eaff21@localhost \
    --to=hagen@jauu.net \
    --cc=davem@davemloft.net \
    --cc=hkjerry.chu@gmail.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pekkas@netcore.fi \
    --cc=tsunanet@gmail.com \
    --cc=yoshfuji@linux-ipv6.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.