From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Stephan Eisvogel <eisvogel-lkml@hawo.stw.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18pre3+patches stalls machine under heavy NFS load
Date: 14 Jan 2002 19:28:10 +0100 [thread overview]
Message-ID: <shsr8osiy85.fsf@charged.uio.no> (raw)
In-Reply-To: <2144085514.20020114164200@hawo.stw.uni-erlangen.de>
In-Reply-To: <2144085514.20020114164200@hawo.stw.uni-erlangen.de>
>>>>> " " == Stephan Eisvogel <eisvogel-lkml@hawo.stw.uni-erlangen.de> writes:
> Hello, first post.
> Summary: Experiencing machine stalls with 2.4.18pre3 with huge
> cache when bonnie is working on mounted NFS over Fast Ethernet.
Yes. I didn't realize that sync_page() gets called with
TASK_UNINTERRUPTIBLE set. When I added in a preemption point in
__rpc_execute() it was causing the hang.
Fixed now...
Cheers,
Trond
prev parent reply other threads:[~2002-01-14 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 15:42 2.4.18pre3+patches stalls machine under heavy NFS load Stephan Eisvogel
2002-01-14 18:28 ` Trond Myklebust [this message]
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=shsr8osiy85.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=eisvogel-lkml@hawo.stw.uni-erlangen.de \
--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