linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Markus <M4rkusXXL@web.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Zdenek Kabelac <zkabelac@redhat.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Lukas Hejtmanek <xhejtman@ics.muni.cz>
Subject: Re: drop_caches ...
Date: Thu, 5 Mar 2009 21:36:03 +0800	[thread overview]
Message-ID: <20090305133603.GA22442@localhost> (raw)
In-Reply-To: <200903051255.35407.M4rkusXXL@web.de>

Hi Markus,

On Thu, Mar 05, 2009 at 01:55:35PM +0200, Markus wrote:
> > Markus, you may want to try this patch, it will have better chance to figure out
> > the hidden file pages.
> > 
> > 1) apply the patch and recompile kernel with CONFIG_PROC_FILECACHE=m
> > 2) after booting:
> >         modprobe filecache
> >         cp /proc/filecache filecache-`date +'%F'`
> > 3) send us the copied file, it will list all cached files, including
> >    the normally hidden ones.
> 
> The file consists of 674 lines. If I interpret it right, "size" is the 
> filesize and "cached" the amount of the file being in cache (why can 
> this be bigger than the file?!).

          size = file size in bytes
        cached = cached pages

So it's normal that (size > cached).

Thanks,
Fengguang

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2009-03-05 13:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903041057.34072.M4rkusXXL@web.de>
     [not found] ` <200903041132.04451.M4rkusXXL@web.de>
     [not found]   ` <20090304110558.GA17014@localhost>
     [not found]     ` <200903041229.41482.M4rkusXXL@web.de>
2009-03-04 11:57       ` drop_caches Wu Fengguang
2009-03-04 12:32         ` drop_caches Zdenek Kabelac
2009-03-04 13:47           ` drop_caches Markus
2009-03-04 14:09             ` drop_caches Zdenek Kabelac
2009-03-04 18:47               ` drop_caches Markus
2009-03-05  0:48                 ` drop_caches Wu Fengguang
2009-03-05  9:06                   ` drop_caches Lukas Hejtmanek
2009-03-05  9:14                     ` drop_caches KOSAKI Motohiro
2009-03-05 11:11                       ` drop_caches Wu Fengguang
2009-03-05 11:55                   ` drop_caches Markus
2009-03-05 13:29                     ` drop_caches Wu Fengguang
2009-03-05 14:05                       ` drop_caches Markus
2009-03-05 14:22                         ` drop_caches Wu Fengguang
2009-03-05 14:43                           ` drop_caches Markus
2009-03-05 14:52                             ` drop_caches Wu Fengguang
2009-03-05 13:36                     ` Wu Fengguang [this message]
2009-03-05 13:45                       ` drop_caches Lukas Hejtmanek
2009-03-05 13:48                         ` drop_caches Wu Fengguang
2009-03-05 13:50                       ` drop_caches Markus
2009-03-05 14:01                       ` drop_caches Lukas Hejtmanek
2009-03-05 14:07                         ` drop_caches Wu Fengguang
     [not found] <20090304123836.GA13706@ics.muni.cz>
2009-03-04 12:54 ` drop_caches Wu Fengguang

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=20090305133603.GA22442@localhost \
    --to=fengguang.wu@intel.com \
    --cc=M4rkusXXL@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=xhejtman@ics.muni.cz \
    --cc=zkabelac@redhat.com \
    /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