From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jesper Krogh <jesper-Q2TZfHgGEy4@public.gmane.org>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Greg Banks <gnb-xTcybq6BZ68@public.gmane.org>
Subject: Re: 2.6.31 under "heavy" NFS load.
Date: Mon, 23 Nov 2009 16:27:26 -0500 [thread overview]
Message-ID: <20091123212726.GC8534@fieldses.org> (raw)
In-Reply-To: <4B05A91D.1090305-Q2TZfHgGEy4@public.gmane.org>
On Thu, Nov 19, 2009 at 09:22:53PM +0100, Jesper Krogh wrote:
> Ok, I still haven't had the "excact same" workload put on the host, but
> it has been running on the patched kernel for 8 days now and I havent
> seen load numbers over 32 while service 1100MB/s over NFS (dd'ing 512
> bytes blocks out of the server from the clients) while doing local disk
> IO for an iowait of ~25% (4 cores sucking what they can). This workload
> is "similar" to the one sending it to load numbers of over 100 earlier.
>
> So I'm confident that the problem is solved by reverting the patch.
OK, I'm applying the revert for 2.6.33.
--b.
WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jesper Krogh <jesper@krogh.cc>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Greg Banks <gnb@fmeh.org>
Subject: Re: 2.6.31 under "heavy" NFS load.
Date: Mon, 23 Nov 2009 16:27:26 -0500 [thread overview]
Message-ID: <20091123212726.GC8534@fieldses.org> (raw)
In-Reply-To: <4B05A91D.1090305@krogh.cc>
On Thu, Nov 19, 2009 at 09:22:53PM +0100, Jesper Krogh wrote:
> Ok, I still haven't had the "excact same" workload put on the host, but
> it has been running on the patched kernel for 8 days now and I havent
> seen load numbers over 32 while service 1100MB/s over NFS (dd'ing 512
> bytes blocks out of the server from the clients) while doing local disk
> IO for an iowait of ~25% (4 cores sucking what they can). This workload
> is "similar" to the one sending it to load numbers of over 100 earlier.
>
> So I'm confident that the problem is solved by reverting the patch.
OK, I'm applying the revert for 2.6.33.
--b.
next prev parent reply other threads:[~2009-11-23 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 19:30 2.6.31 under "heavy" NFS load Jesper Krogh
2009-11-09 19:30 ` Jesper Krogh
[not found] ` <4AF86DE4.5010607-Q2TZfHgGEy4@public.gmane.org>
2009-11-10 18:41 ` J. Bruce Fields
2009-11-10 18:41 ` J. Bruce Fields
2009-11-10 19:05 ` Jesper Krogh
2009-11-10 19:05 ` Jesper Krogh
2009-11-19 20:22 ` Jesper Krogh
[not found] ` <4B05A91D.1090305-Q2TZfHgGEy4@public.gmane.org>
2009-11-23 21:27 ` J. Bruce Fields [this message]
2009-11-23 21:27 ` J. Bruce Fields
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=20091123212726.GC8534@fieldses.org \
--to=bfields@fieldses.org \
--cc=gnb-xTcybq6BZ68@public.gmane.org \
--cc=jesper-Q2TZfHgGEy4@public.gmane.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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 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.