From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Peter Leckie <pleckie@sgi.com>
Cc: talpey@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 01/04] NFS/RDMA client stall patches
Date: Tue, 10 Jun 2008 15:24:59 -0400 [thread overview]
Message-ID: <1213125899.20459.34.camel@localhost> (raw)
In-Reply-To: <4830F91C.7070206@sgi.com>
On Mon, 2008-05-19 at 13:50 +1000, Peter Leckie wrote:
> Don't call __xprt_get_cong() if this is a retransmit.
> This prevents __xprt_get_cong() from recursively
> incrementing the congestion avoidance window for
> retransmitted data.
>
> Signed-off-by: Peter Leckie <pleckie-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
> Reviewed-by: Greg Banks <gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
> X-Sgi-Pv: 971446
> <http://bugworks/query.cgi/971446>---
> Index: linux-2.6.25.3/net/sunrpc/xprt.c
> ===================================================================
> --- linux-2.6.25.3.orig/net/sunrpc/xprt.c
> +++ linux-2.6.25.3/net/sunrpc/xprt.c
> @@ -224,7 +224,8 @@ int xprt_reserve_xprt_cong(struct rpc_ta
> return 1;
> goto out_sleep;
> }
> - if (__xprt_get_cong(xprt, task)) {
> + /*If this is a retransmit don't increment cong*/
> + if ((req && req->rq_ntrans) ||__xprt_get_cong(xprt, task)) {
> xprt->snd_task = task;
> if (req) {
> req->rq_bytes_sent = 0;
>
Why would we not want to increment the congestion avoidance window on
retransmitted data? On timeout, xprt_adjust_cwnd will call
__xprt_put_cong() prior to the retransmission, so I can't see how this
is a 'recursive increment'.
Trond
next prev parent reply other threads:[~2008-06-10 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 3:50 [PATCH 01/04] NFS/RDMA client stall patches Peter Leckie
2008-06-10 19:24 ` Trond Myklebust [this message]
2008-06-11 8:03 ` Peter Leckie
2008-06-11 13:53 ` Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDaogxL000001eb-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-06-12 8:45 ` Peter Leckie
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=1213125899.20459.34.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=linux-nfs@vger.kernel.org \
--cc=pleckie@sgi.com \
--cc=talpey@netapp.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.