public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kladit@t-online.de (Klaus Dittrich)
To: Andrew Morton <akpm@osdl.org>
Cc: Klaus Dittrich <kladit@t-online.de>, linux-kernel@vger.kernel.org
Subject: Re: dentry cache leak? Re: rsync out of memory 2.6.8-rc2
Date: Mon, 26 Jul 2004 22:02:04 +0200	[thread overview]
Message-ID: <4105633C.3080204@xeon2.local.here> (raw)
In-Reply-To: <20040726123702.222ae654.akpm@osdl.org>

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.
>>    
>>
>
>Dammit, -bk7 to -bk8 is a 1.8M diff.  Relevant changes include the switch
>to the rcu callbacks (make them take an rcu_head* rather than a void*) and
>the introduction of /proc/sys/vm/vfs_cache_pressure.
>
>So the immediate question is: please check the contents of your
>vfs_cache_pressure tunable.  It should be 100.  A setting of zero would
>cause this behaviour.
>
>  
>
>> Compiler gcc-3.4.1 
>>    
>>
>
>It would be useful to try a different compiler version.
>
>There's _something_ different in your setup.  If we can work out what this
>factor is, it will lead us to the bug.
>
>  
>

cat /proc/sys/vm/vfs_cache_pressure shows 100.
Should I try an older or newer compiler ?


  reply	other threads:[~2004-07-26 20:35 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 [this message]
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
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=4105633C.3080204@xeon2.local.here \
    --to=kladit@t-online.de \
    --cc=akpm@osdl.org \
    --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