mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jack marrow <jackmarrow2@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: Memory usage per memory zone
Date: Thu, 12 Mar 2009 12:38:46 +0100	[thread overview]
Message-ID: <e2dc2c680903120438i27e209c2h28c61704299b8b4f@mail.gmail.com> (raw)
In-Reply-To: <20090312103847.GA20210@localhost>

> Can you paste the /proc/meminfo after doing 'echo 3 > drop_caches'?

http://pastebin.com/mce24730

>> I thought the kernel dropped caches if a program needs the ram?
>
> Sure, but something is unreclaimable... Maybe some process is taking a
> lot of shared memory(shm)? What's the output of `lsof`?

I can't paste that, but I expect oracle is using it.

>
>> >
>> > MemTotal:      1034496 kB
>> > MemFree:         95600 kB
>> > Buffers:         49916 kB
>> > Cached:         761544 kB
>> > SwapCached:          0 kB
>> > Active:          80484 kB
>> > Inactive:       749960 kB
>> > HighTotal:      131008 kB
>> > HighFree:        68480 kB
>> > LowTotal:       903488 kB
>> > LowFree:         27120 kB
>> > SwapTotal:     2040212 kB
>> > SwapFree:      2039780 kB
>> > Dirty:               4 kB
>> > Writeback:           0 kB
>> > Mapped:          32636 kB
>> > Slab:            93856 kB
>> > CommitLimit:   2557460 kB
>> > Committed_AS:   129980 kB
>> > PageTables:       1800 kB
>> > VmallocTotal:   106488 kB
>> > VmallocUsed:      3372 kB
>> > VmallocChunk:   102616 kB
>> > HugePages_Total:     0
>> > HugePages_Free:      0
>> > Hugepagesize:     2048 kB
>> >
>> > Is upgrading the kernel an option for you?
>>
>> No :(
>>
>> I think shoving some more ram in the box is the best doable option.
>> Would this help here?
>
> There have been huge amounts of change sets in mm area since 2.6.9...
>
>> To do that I need to say "look at how much cache we are using for
>> files, that cache is in the high mem zone (look here) so let's put
>> some more ram in". Does the cache always live in the high mem zone?
>
> Both highmem and normal zones will be used for caches.
>
> Thanks,
> Fengguang
>
>

Thanks.

  reply	other threads:[~2009-03-12 11:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 10:41 jack marrow
2009-03-11 11:43 ` Wu Fengguang
2009-03-11 11:51   ` jack marrow
2009-03-11 12:11     ` Wu Fengguang
2009-03-11 12:16       ` jack marrow
2009-03-11 12:26         ` Wu Fengguang
2009-03-12  7:53           ` jack marrow
2009-03-12  7:59             ` Wu Fengguang
     [not found]               ` <e2dc2c680903120104h4d19a3f6j57ad045bc06f9a90@mail.gmail.com>
     [not found]                 ` <20090312081113.GA19506@localhost>
2009-03-12  8:48                   ` jack marrow
2009-03-12 11:14                     ` Wu Fengguang
2009-03-12 11:39                       ` jack marrow
     [not found]                   ` <e2dc2c680903120117j7be962b2xd63f3296f8f65a46@mail.gmail.com>
2009-03-12 10:38                     ` Wu Fengguang
2009-03-12 11:38                       ` jack marrow [this message]
2009-03-12 11:48                         ` jack marrow
2009-03-12 12:06                           ` Wu Fengguang
2009-03-12 11:51                         ` Wu Fengguang
2009-03-12 12:01                           ` jack marrow
2009-03-11 13:39 ` Thomas Schoebel-Theuer
2009-03-11 15:06   ` jack marrow

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=e2dc2c680903120438i27e209c2h28c61704299b8b4f@mail.gmail.com \
    --to=jackmarrow2@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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®