Re: drop_caches ...

Markus
2009-03-05T14:05:31Z

> 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