All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.60-mm2
Date: Fri, 14 Feb 2003 09:38:56 +0000	[thread overview]
Message-ID: <20030214093856.GC13845@codemonkey.org.uk> (raw)
In-Reply-To: <20030214013144.2d94a9c5.akpm@digeo.com>

On Fri, Feb 14, 2003 at 01:31:44AM -0800, Andrew Morton wrote:

 > . Considerable poking at the NFS MAP_SHARED OOM lockup.  It is limping
 >   along now, but writeout bandwidth is poor and it is still struggling. 
 >   Needs work.
 > 
 > . There's a one-liner which removes an O(n^2) search in the NFS writeback
 >   path.  It increases writeout bandwidth by 4x and decreases CPU load from
 >   100% to 3%.  Needs work.

I'm puzzled that you've had NFS stable enough to test these.
How much testing has this stuff had? Here 2.5.60+bk clients fall over under
moderate NFS load. (And go splat quickly under high load).

Trying to run things like dbench causes lockups, fsx/fstress made it
reboot, plus the odd 'cheating' errors reported yesterday.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@codemonkey.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.60-mm2
Date: Fri, 14 Feb 2003 09:38:56 +0000	[thread overview]
Message-ID: <20030214093856.GC13845@codemonkey.org.uk> (raw)
In-Reply-To: <20030214013144.2d94a9c5.akpm@digeo.com>

On Fri, Feb 14, 2003 at 01:31:44AM -0800, Andrew Morton wrote:

 > . Considerable poking at the NFS MAP_SHARED OOM lockup.  It is limping
 >   along now, but writeout bandwidth is poor and it is still struggling. 
 >   Needs work.
 > 
 > . There's a one-liner which removes an O(n^2) search in the NFS writeback
 >   path.  It increases writeout bandwidth by 4x and decreases CPU load from
 >   100% to 3%.  Needs work.

I'm puzzled that you've had NFS stable enough to test these.
How much testing has this stuff had? Here 2.5.60+bk clients fall over under
moderate NFS load. (And go splat quickly under high load).

Trying to run things like dbench causes lockups, fsx/fstress made it
reboot, plus the odd 'cheating' errors reported yesterday.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  reply	other threads:[~2003-02-14  9:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14  9:31 2.5.60-mm2 Andrew Morton
2003-02-14  9:31 ` 2.5.60-mm2 Andrew Morton
2003-02-14  9:38 ` Dave Jones [this message]
2003-02-14  9:38   ` 2.5.60-mm2 Dave Jones
2003-02-14  9:58   ` 2.5.60-mm2 Andrew Morton
2003-02-14  9:58     ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:13     ` 2.5.60-mm2 Dave Jones
2003-02-14 10:13       ` 2.5.60-mm2 Dave Jones
2003-02-14 10:22       ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:22         ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:10   ` 2.5.60-mm2 Thomas Schlichter
2003-02-17  1:59     ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:08       ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:35         ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 12:35           ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 18:32           ` 2.5.60-mm2 Bill Davidsen
2003-02-17 18:32             ` 2.5.60-mm2 Bill Davidsen
2003-02-14 20:59 ` compile fail: 2.5.60-mm2 Core
2003-02-14 21:18   ` Joshua Kwan
2003-02-14 22:06   ` Andrew Morton
2003-02-14 22:06     ` Andrew Morton
2003-02-15 20:27 ` 2.5.60-mm2 Arador
2003-02-15 20:27   ` 2.5.60-mm2 Arador
  -- strict thread matches above, loose matches on Subject: below --
2003-02-14 13:02 2.5.60-mm2 Con Kolivas

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=20030214093856.GC13845@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.