netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Allen Simpson <william.allen.simpson@gmail.com>
To: Andreas Petlund <apetlund@simula.no>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	shemminger@vyatta.com, ilpo.jarvinen@helsinki.fi,
	davem@davemloft.net
Subject: Re: [PATCH 2/3] net: TCP thin linear timeouts
Date: Tue, 27 Oct 2009 23:20:39 -0400	[thread overview]
Message-ID: <4AE7B887.6090806@gmail.com> (raw)
In-Reply-To: <4AE72079.4030504@simula.no>

Sorry to be too picky about the naming, but "rm_expb" really doesn't
mean what is actually done.  Perhaps TCP_THIN_LINEAR_BACKOFF and
sysctl_tcp_thin_linear_backoff?

Also, as debated on some other recent patches, shouldn't the global
sysctl specify the default, and the per socket option specify the
forced override?

  parent reply	other threads:[~2009-10-28  3:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 16:31 [PATCH 2/3] net: TCP thin linear timeouts Andreas Petlund
2009-10-27 16:56 ` Eric Dumazet
2009-10-28 12:58   ` Arnd Hannemann
2009-10-28 14:31     ` Ilpo Järvinen
2009-10-29 13:51       ` Andreas Petlund
2009-10-29 14:24         ` Eric Dumazet
2009-10-29 17:01         ` Rick Jones
     [not found]     ` <07CD1135-C68B-4264-8CD3-C4BC0400FDA2@simula.no>
2009-10-29 16:11       ` Arnd Hannemann
2009-10-28  3:20 ` William Allen Simpson [this message]
2009-10-29 13:50   ` Andreas Petlund
2009-10-28 14:18 ` Ilpo Järvinen
  -- strict thread matches above, loose matches on Subject: below --
2009-10-29 15:14 apetlund
2009-10-29 15:19 apetlund
2009-10-29 15:43 apetlund
2009-10-29 15:50 ` Eric Dumazet
2009-10-29 20:52 ` Ilpo Järvinen
2009-10-29 16:54 apetlund
2009-10-30 10:48 apetlund
2009-10-30 17:33 ` Rick Jones
2009-10-30 18:11   ` William Allen Simpson
2009-11-05 13:37     ` Andreas Petlund
2009-10-30 15:27 apetlund

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=4AE7B887.6090806@gmail.com \
    --to=william.allen.simpson@gmail.com \
    --cc=apetlund@simula.no \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).