mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kunal Trivedi" <ktrivedilkml@gmail.com>
To: linuxkernel <linux-kernel@vger.kernel.org>
Subject: Re: dentry cache grows to really large number on 64bit machine
Date: Wed, 6 Dec 2006 23:21:36 -0800	[thread overview]
Message-ID: <a10e25a30612062321n5f01ed91y3095a0ad0f8cfee8@mail.gmail.com> (raw)
In-Reply-To: <a10e25a30612061505i4e9ea428g473d5bead437845a@mail.gmail.com>

Hi,
Another piece of information...
If i do on shell.

# while 1
# ./grow_dentry
# end
(grow_dentry is C code I've posted in previous msg.)

Then dentry_cache grows really fast.

But if within 'C' code if I write while(1), then everything is okay.
(No substantial growth ).

Thanks
-Kunal

On 12/6/06, Kunal Trivedi <ktrivedilkml@gmail.com> wrote:
> Hi,
> I am running 2.6.18 kernel on 64 bit AMD machine. (procinfo attached
> at the end of the mail). One of the things I have noticed that
> dentry_cache grows really fast under certain code path.
> So, far I have not seen any problems, but I would like to get some
> more input on this subject. Is it okay for dentry_cache to grow that
> much ?
>
> I've run following program for an ~1.00 hour. And my slabinfo shows following.
>
> # cat /proc/slabinfo | grep dentry
> dentry_cache      5228333 5228333    224   17    1 : tunables  120
> 60    8 : slabdata 307549 307549      0
>
>
> # cat /proc/meminfo
> MemTotal:      8173080 kB
> MemFree:       6787852 kB
> Buffers:         42048 kB
> Cached:          72616 kB
> SwapCached:          0 kB
> Active:          88608 kB
> Inactive:        29796 kB
> HighTotal:           0 kB
> HighFree:            0 kB
> LowTotal:      8173080 kB
> LowFree:       6787852 kB
> SwapTotal:     2096472 kB
> SwapFree:      2096472 kB
> Dirty:              48 kB
> Writeback:           0 kB
> AnonPages:        3716 kB
> Mapped:           3336 kB
> Slab:          1251292 kB
> PageTables:        192 kB
> NFS_Unstable:        0 kB
> Bounce:              0 kB
> CommitLimit:  10269552 kB
> Committed_AS:    11500 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed:      1272 kB
> VmallocChunk: 34359737015 kB
> HugePages_Total:     0
> HugePages_Free:      0
> HugePages_Rsvd:      0
> Hugepagesize:     2048 kB
>
>
> int
> main()
> {
>     int fd;
>     char fname[] = "/tmp/proc-output-XXXXXX";
>
>     fd = mkstemp(fname);
>     close(fd);
>     unlink(fname);
>     return 0;
> }
>
> Please advice,
>
> Thanks
> -Kunal
>

      reply	other threads:[~2006-12-07  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 23:05 Kunal Trivedi
2006-12-07  7:21 ` Kunal Trivedi [this message]

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=a10e25a30612062321n5f01ed91y3095a0ad0f8cfee8@mail.gmail.com \
    --to=ktrivedilkml@gmail.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

all inboxes | Powered by JetHome®