From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andreas Pfaller <apfaller@yahoo.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.20-pre8-ac3: NFS performance regression
Date: 04 Oct 2002 00:50:04 +0200 [thread overview]
Message-ID: <shsu1k316jn.fsf@charged.uio.no> (raw)
In-Reply-To: <1033683184.28814.35.camel@irongate.swansea.linux.org.uk>
>>>>> " " == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Thu, 2002-10-03 at 19:32, Andreas Pfaller wrote:
>> However I noticed a significant NFS performance drop with
>> 2.4.20-pre8-ac3. Other network throughput is not affected.
> I see this with all recent 2.4.20pre and 2.4.20pre-ac
> kernels. I've not had time to retest with Trond's fixes to
> recheck it all
FYI, here is the 'fix' Alan is talking about. It could be worth
trying...
Cheers,
Trond
--- 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 prev parent reply other threads:[~2002-10-03 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 18:32 Andreas Pfaller
2002-10-03 22:13 ` Alan Cox
2002-10-03 22:50 ` Trond Myklebust [this message]
2002-10-03 23:15 ` Andreas Pfaller
2002-10-03 23:40 ` Bryan O'Sullivan
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=shsu1k316jn.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apfaller@yahoo.com.au \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®