mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leigh Orf <orf@mailbag.com>
To: Ken Brownfield <brownfld@irridia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 memory badness (reproducible)
Date: Sat, 08 Dec 2001 13:54:17 -0500	[thread overview]
Message-ID: <200112081854.fB8IsIr01485@orp.orf.cx> (raw)
In-Reply-To: Your message of "Sat, 08 Dec 2001 09:56:20 CST." <20011208095620.C1179@asooo.flowerfire.com>



Ken Brownfield wrote:

|   This parallels what I'm seeing -- perhaps inode/dentry cache
|   bloat is causing the memory issue (which mimics if not _is_
|   a memory leak) _and_ my kswapd thrashing?  It fits both the
|   situation you report and what I'm seeing with I/O across a
|   large number of files (inodes) -- updatedb, smb, NFS, etc.
|
|   I think Andrea was on to this issue, so I'm hoping his work
|   will help.  Have you tried an -aa kernel or an aa patch onto
|   a 2.4.17-pre4 to see how the kernel's behavior changes?
|   
|   -- 
|   Ken.
|   brownfld@irridia.com

I get the exact same behavior with 2.4.17-pre4-aa1 - many applications
abort with ENOMEM after updatedb (filling the buffer and cache). Is
there another kernel/patch I should try?

Leigh Orf


  reply	other threads:[~2001-12-08 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-08 15:39 Leigh Orf
2001-12-08 15:56 ` Ken Brownfield
2001-12-08 18:54   ` Leigh Orf [this message]
2001-12-08 19:41     ` Andrew Morton
2001-12-08 20:04       ` Leigh Orf
2001-12-08 21:42         ` Leigh Orf
2001-12-08 22:24           ` Leigh Orf
2001-12-11 19:07           ` Hugh Dickins
2001-12-11 22:13             ` H. Peter Anvin
2001-12-11 22:59             ` Andrea Arcangeli
2001-12-12 14:51               ` Leigh Orf
2001-12-18 14:27               ` Holger Lubitz
2001-12-11 20:04           ` Stephan von Krawczynski

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=200112081854.fB8IsIr01485@orp.orf.cx \
    --to=orf@mailbag.com \
    --cc=brownfld@irridia.com \
    --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

Powered by JetHome