linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Markus <M4rkusXXL@web.de>
To: linux-kernel@vger.kernel.org
Cc: Wu Fengguang <fengguang.wu@intel.com>,
	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 15:05:26 +0100	[thread overview]
Message-ID: <200903051505.26584.M4rkusXXL@web.de> (raw)
In-Reply-To: <20090305132906.GA22524@localhost>

> Could you please try the attached patch which will also show the
> user and process that opened these files? It adds three more fields
> when CONFIG_PROC_FILECACHE_EXTRAS is selected.
> 
> Thanks,
> Fengguang
>  
> On Thu, Mar 05, 2009 at 01:55:35PM +0200, Markus wrote:
> > 
> > # sort -n -k 3 filecache-2009-03-05 | tail -n 5
> >      15886       7112     7112     100      1    d- 00:08
> > (tmpfs)        /dev/zero\040(deleted)
> >      16209      35708    35708     100      1    d- 00:08
> > (tmpfs)        /dev/zero\040(deleted)
> >      16212      82128    82128     100      1    d- 00:08
> > (tmpfs)        /dev/zero\040(deleted)
> >      15887     340024   340024     100      1    d- 00:08
> > (tmpfs)        /dev/zero\040(deleted)
> >      15884     455008   455008     100      1    d- 00:08
> > (tmpfs)        /dev/zero\040(deleted)
> > 
> > The sum of the third column is 1013 MB.
> > To note the biggest ones (or do you want the whole file?)... and 
thats 
> > after a sync and a drop_caches! (Can be seen in the commands given.)

I could, but I know where these things belong to. Its from sphinx (a 
mysql indexer) searchd. It loads parts of the index into memory.
The sizes looked well-known and killing the searchd will reduce "cached" 
to a normal amount ;)

I just dont know why its in "cached" (can that be swapped out btw?).
But I think thats not a problem of the kernel, but of anonymous 
mmap-ing.

I think its resolved, thanks to everybody and Fengguang in particular!

Markus

--
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>

  reply	other threads:[~2009-03-05 14:05 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                       ` Markus [this message]
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                     ` drop_caches Wu Fengguang
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=200903051505.26584.M4rkusXXL@web.de \
    --to=m4rkusxxl@web.de \
    --cc=fengguang.wu@intel.com \
    --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