All of lore.kernel.org
 help / color / mirror / Atom feed
From: Howard Chu <hyc@symas.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mmap vs fs cache
Date: Wed, 06 Mar 2013 02:14:11 -0800	[thread overview]
Message-ID: <513716F3.4070100@symas.com> (raw)
In-Reply-To: <513685D6.7080102@symas.com>

Howard Chu wrote:
> Howard Chu wrote:
>> 2 questions:
>>      why is there data in the FS cache that isn't owned by (the mmap of) the
>> process that caused it to be paged in in the first place?
>>      is there a tunable knob to discourage the page cache from stealing from the
>> process?
>
> This Unmapped page cache control http://lwn.net/Articles/436010/ sounds like
> it might have been helpful here. I.e., having a way to prioritize so that
> unmapped cache pages get reclaimed in preference to mapped pages could help.
> Though I still don't understand why these pages in the cache aren't mapped in
> the first place.
>
As implied by this post 
http://lkml.indiana.edu/hypermail/linux/kernel/0701.3/0354.html setting 
swappiness to 0 seems to give the desired effect of preventing mapped pages 
from being reclaimed. If this is an intended effect, it would be nice to have 
this documented in Documentation/sysctl/vm.txt. If this is not the intended 
effect, please don't "fix" this without providing a supported means of doing 
the same.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

  reply	other threads:[~2013-03-06 10:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 17:57 mmap vs fs cache Howard Chu
2013-03-05 23:55 ` Howard Chu
2013-03-06 10:14   ` Howard Chu [this message]
2013-03-06 10:22     ` Howard Chu
2013-03-07 15:43 ` Jan Kara
2013-03-07 15:43   ` Jan Kara
2013-03-08  2:08   ` Johannes Weiner
2013-03-08  2:08     ` Johannes Weiner
2013-03-08  7:46     ` Howard Chu
2013-03-08  7:46       ` Howard Chu
2013-03-08  8:42       ` Kirill A. Shutemov
2013-03-08  8:42         ` Kirill A. Shutemov
2013-03-08  9:40         ` Howard Chu
2013-03-08  9:40           ` Howard Chu
2013-03-08 14:47           ` Chris Friesen
2013-03-08 14:47             ` Chris Friesen
2013-03-08 15:00             ` Howard Chu
2013-03-08 15:00               ` Howard Chu
2013-03-08 15:25               ` Chris Friesen
2013-03-08 15:25                 ` Chris Friesen
2013-03-08 16:16               ` Johannes Weiner
2013-03-08 16:16                 ` Johannes Weiner
2013-03-08 20:04                 ` Howard Chu
2013-03-08 20:04                   ` Howard Chu
2013-03-11 12:04                   ` Jan Kara
2013-03-11 12:04                     ` Jan Kara
2013-03-11 12:40                     ` Howard Chu
2013-03-11 12:40                       ` Howard Chu
2013-03-09  3:28                 ` Ric Mason
2013-03-09  3:28                   ` Ric Mason
2013-03-09  1:22               ` Phillip Susi
2013-03-09  1:22                 ` Phillip Susi
2013-03-11 11:52                 ` Jan Kara
2013-03-11 11:52                   ` Jan Kara
2013-03-11 15:03                   ` Phillip Susi
2013-03-11 15:03                     ` Phillip Susi
2013-03-09  2:34     ` Ric Mason
2013-03-09  2:34       ` Ric Mason

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=513716F3.4070100@symas.com \
    --to=hyc@symas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.