netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] make _minimum_ TCP retransmission timeout configurable take 2
Date: Fri, 31 Aug 2007 15:20:52 -0700	[thread overview]
Message-ID: <46D89444.3080508@hp.com> (raw)
In-Reply-To: <20070831.143855.88699905.davem@davemloft.net>

David Miller wrote:
> From: Rick Jones <rick.jones2@hp.com>
> Date: Fri, 31 Aug 2007 13:59:50 -0700
> 
> 
>>ip is at tcp_rto_min+0x20/0x40
> 
> 
> diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
> index 1ee7212..bbad2cd 100644
> --- a/net/ipv4/tcp_input.c
> +++ b/net/ipv4/tcp_input.c
> @@ -560,7 +560,7 @@ static u32 tcp_rto_min(struct sock *sk)
>  	struct dst_entry *dst = __sk_dst_get(sk);
>  	u32 rto_min = TCP_RTO_MIN;
>  
> -	if (dst_metric_locked(dst, RTAX_RTO_MIN))
> +	if (dst && dst_metric_locked(dst, RTAX_RTO_MIN))
>  		rto_min = dst->metrics[RTAX_RTO_MIN-1];
>  	return rto_min;
>  }

Applied and beating on it with a while loop doing a bunch of ip route 
del add change stuff while netperf TCP_CRR tests are running.  Thusfar 
things seem OK wrt the system staying alive, but since I only saw the 
failure once I'm not sure how much that is really saying.

I'm going to go ahead and take a look at input vs output units and 
differences between those with rto_min vs rtt.

rick jones

  reply	other threads:[~2007-08-31 22:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31  0:09 [PATCH] make _minimum_ TCP retransmission timeout configurable take 2 Rick Jones
2007-08-31  0:39 ` David Miller
2007-08-31  1:07   ` Rick Jones
2007-08-31  4:52     ` John Heffner
2007-08-31 17:19       ` Rick Jones
2007-08-31  5:09     ` David Miller
2007-08-31 18:11       ` Rick Jones
2007-08-31 18:57         ` David Miller
2007-08-31 20:59           ` Rick Jones
2007-08-31 21:38             ` David Miller
2007-08-31 22:20               ` Rick Jones [this message]
2007-08-31 22:24                 ` David Miller

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=46D89444.3080508@hp.com \
    --to=rick.jones2@hp.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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 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).