All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>, Andrew Morton <akpm@digeo.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: ZONE_NORMAL exhaustion (dcache slab)
Date: Thu, 24 Oct 2002 07:35:48 -0400	[thread overview]
Message-ID: <200210240735.48973.tomlins@cam.org> (raw)
In-Reply-To: <2622146086.1035233637@[10.10.2.3]>

Hi,

I just experienced this problem on UP with 513M memory.  About 400m was 
locked in dentries.  The system was very unresponsive - suspect it was
spending gobs of time scaning unfreeable dentries.  This was with -mm3
up about 24 hours.

The inode caches looked sane.  Just the dentries were out of wack.

Ed


WARNING: multiple messages have this Message-ID (diff)
From: Ed Tomlinson <tomlins@cam.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>, Andrew Morton <akpm@digeo.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: ZONE_NORMAL exhaustion (dcache slab)
Date: Thu, 24 Oct 2002 07:35:48 -0400	[thread overview]
Message-ID: <200210240735.48973.tomlins@cam.org> (raw)
In-Reply-To: <2622146086.1035233637@[10.10.2.3]>

Hi,

I just experienced this problem on UP with 513M memory.  About 400m was 
locked in dentries.  The system was very unresponsive - suspect it was
spending gobs of time scaning unfreeable dentries.  This was with -mm3
up about 24 hours.

The inode caches looked sane.  Just the dentries were out of wack.

Ed

--
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/

  parent reply	other threads:[~2002-10-24 11:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 20:40 ZONE_NORMAL exhaustion (dcache slab) Martin J. Bligh
2002-10-21 20:40 ` Martin J. Bligh
2002-10-21 21:13 ` Andrew Morton
2002-10-21 21:13   ` Andrew Morton
2002-10-21 21:16   ` Martin J. Bligh
2002-10-21 21:16     ` Martin J. Bligh
2002-10-21 21:33     ` Andrew Morton
2002-10-21 21:33       ` Andrew Morton
2002-10-21 21:33       ` Martin J. Bligh
2002-10-21 21:33         ` Martin J. Bligh
2002-10-21 21:49         ` Andrew Morton
2002-10-21 21:49           ` Andrew Morton
2002-10-21 22:30         ` Rik van Riel
2002-10-21 22:30           ` Rik van Riel
2002-10-21 22:53           ` Andrew Morton
2002-10-21 22:53             ` Andrew Morton
2002-10-22  0:31             ` Martin J. Bligh
2002-10-22  0:31               ` Martin J. Bligh
2002-10-22  3:39               ` Andrew Morton
2002-10-22  3:39                 ` Andrew Morton
2002-10-22  3:53                 ` Martin J. Bligh
2002-10-22  3:53                   ` Martin J. Bligh
2002-10-22  4:20                   ` Andrew Morton
2002-10-22  4:20                     ` Andrew Morton
2002-10-22  5:49                     ` Martin J. Bligh
2002-10-22  5:49                       ` Martin J. Bligh
2002-10-22  6:21                       ` Andrew Morton
2002-10-22  6:21                         ` Andrew Morton
2002-10-22 16:13                         ` Martin J. Bligh
2002-10-22 16:13                           ` Martin J. Bligh
2002-10-24 11:35                   ` Ed Tomlinson [this message]
2002-10-24 11:35                     ` Ed Tomlinson
2002-10-24 14:28                     ` Martin J. Bligh
2002-10-24 14:28                       ` Martin J. Bligh
2002-10-22 16:33             ` Rik van Riel
2002-10-22 16:33               ` Rik van Riel
2002-10-22 16:54               ` ARP address resolving in kernel Steffen Persvold
2002-10-22 17:05               ` ZONE_NORMAL exhaustion (dcache slab) Andrew Morton
2002-10-22 17:05                 ` Andrew Morton
2002-10-22 16:21       ` Dipankar Sarma
2002-10-22 16:21         ` Dipankar Sarma

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=200210240735.48973.tomlins@cam.org \
    --to=tomlins@cam.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.com \
    --cc=riel@conectiva.com.br \
    /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.