public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Andrew Morton <akpm@osdl.org>
Cc: kladit@t-online.de, linux-kernel@vger.kernel.org
Subject: Re: dentry cache leak? Re: rsync out of memory 2.6.8-rc2
Date: Fri, 30 Jul 2004 23:01:27 -0300	[thread overview]
Message-ID: <20040731020127.GC4798@logos.cnet> (raw)
In-Reply-To: <20040730124744.0eb11f63.akpm@osdl.org>

On Fri, Jul 30, 2004 at 12:47:44PM -0700, Andrew Morton wrote:
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
> >
> > On Thu, Jul 29, 2004 at 02:07:43PM -0700, Andrew Morton wrote:
> > > kladit@t-online.de (Klaus Dittrich) wrote:
> > > >
> > > > >Can you narrow the onset of the problem down to any particular kernel
> > > > >snapshot?
> > > > 
> > > > Did it and here is the answer.
> > > > 
> > > > kernel-2.6.7 and bk's up to 2.6.7-bk7 survived a du -s,
> > > > kernels starting with 2.6.7-bk8 did not.
> > > 
> > > I can reproduce this oom btw.  Am (very, very slowly) working out what's
> > > causing it.  It's unrelated to the vfs-cache-pressure patch.  I'd hope to
> > > have it fixed up for 2.6.8. 
> > 
> > Odd, because the only thing I can see which affects dcache related code
> > between -bk7 and -bk8 is the vfs-cache-pressure patch.
> 
> It can be triggered with that patch reverted.
> 
> > What are the exact steps you're using to reproduce the leak?
> 
> Just a `du -s' over zillions of files on a 2G machine.
> 
> > And where do you think the problem lies?
> 
> Seems that we reach a state where lowmem pagecache get reclaimed faster
> than dcache/icache.  This causes the number of pages scanned for lowmem
> allocations to fall.  This causes less scanning of the slab and the whole
> thing repeats.  I expect changing nr_used_zone_pages() to ignore highmem
> will fix it, and might be the long-term fix, too.

I'll try making that change to nr_used_zone_pages() tomorrow morning and see 
what happens. 

But, why does Klaus claim he can't trigger the bug with -bk7 and only -bk8 ? 

  reply	other threads:[~2004-07-31  2:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 15:06 dentry cache leak? Re: rsync out of memory 2.6.8-rc2 Klaus Dittrich
2004-07-26 19:37 ` Andrew Morton
2004-07-26 20:02   ` Klaus Dittrich
2004-07-26 20:38     ` Andrew Morton
2004-07-26 21:39       ` Klaus Dittrich
2004-07-26 22:14         ` Jan-Frode Myklebust
2004-07-27 20:43           ` Klaus Dittrich
2004-07-27 21:05             ` Klaus Dittrich
2004-07-28  1:21               ` Nick Piggin
2004-07-28 15:06                 ` Klaus Dittrich
2004-07-29  3:31                   ` Nick Piggin
2004-07-29 21:07 ` Andrew Morton
2004-07-30 16:30   ` Marcelo Tosatti
2004-07-30 19:47     ` Andrew Morton
2004-07-31  2:01       ` Marcelo Tosatti [this message]
2004-07-31 17:23       ` Linus Torvalds
2004-07-31 21:39         ` Andrew Morton
2004-08-03  6:55           ` Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2004-08-01  9:47 Klaus Dittrich
2004-07-19  9:19 Klaus Dittrich
2004-07-19 11:20 ` dentry cache leak? " bert hubert
     [not found]   ` <20040719113228.GA15295@outpost.ds9a.nl>
2004-07-19 12:56     ` Klaus Dittrich
2004-07-26  1:06       ` Andrew Morton

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=20040731020127.GC4798@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=kladit@t-online.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