From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [BUG] NFS in 2.4.20-pre6+ stalls
Date: Wed, 25 Sep 2002 14:41:37 +0200 [thread overview]
Message-ID: <200209251441.37444.trond.myklebust@fys.uio.no> (raw)
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
> Hi, all. Just noticed this with 2.4.20-pre6 (and -pre7): NFS write
> sometimes (usually) stalls for minutes at a time. This problem wasn't
Richard,
Does the appended patch make a difference?
Cheers,
Trond
[-- Attachment #2: resend.dif --]
[-- Type: text/plain, Size: 910 bytes --]
--- linux/net/sunrpc/xprt.c.orig Fri Aug 30 20:16:17 2002
+++ linux/net/sunrpc/xprt.c Tue Sep 24 00:08:59 2002
@@ -171,10 +171,10 @@
if (xprt->snd_task)
return;
- if (!xprt->nocong && RPCXPRT_CONGESTED(xprt))
- return;
task = rpc_wake_up_next(&xprt->resend);
if (!task) {
+ if (!xprt->nocong && RPCXPRT_CONGESTED(xprt))
+ return;
task = rpc_wake_up_next(&xprt->sending);
if (!task)
return;
@@ -1013,7 +1013,6 @@
}
rpc_inc_timeo(&task->tk_client->cl_rtt);
xprt_adjust_cwnd(req->rq_xprt, -ETIMEDOUT);
- __xprt_put_cong(xprt, req);
}
req->rq_nresend++;
@@ -1150,10 +1149,7 @@
req->rq_bytes_sent = 0;
}
out_release:
- spin_lock_bh(&xprt->sock_lock);
- __xprt_release_write(xprt, task);
- __xprt_put_cong(xprt, req);
- spin_unlock_bh(&xprt->sock_lock);
+ xprt_release_write(xprt, task);
return;
out_receive:
dprintk("RPC: %4d xmit complete\n", task->tk_pid);
next reply other threads:[~2002-09-25 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 12:41 Trond Myklebust [this message]
2002-09-25 15:30 ` [BUG] NFS in 2.4.20-pre6+ stalls Richard Gooch
2002-09-26 11:29 ` Trond Myklebust
2002-09-28 22:43 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2002-09-16 22:54 Richard Gooch
2002-09-16 23:10 ` Alan Cox
2002-09-17 18:41 ` Bill Davidsen
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=200209251441.37444.trond.myklebust@fys.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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).