From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "kautuk.c @samsung.com" <consul.kautuk@gmail.com>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-fsdev@vger.rutgers.edu, linux-kernel@vger.kernel.org
Subject: Re: Is there any way to stop reclamation of file cache pages ?
Date: Thu, 8 Sep 2011 09:26:33 +0900 [thread overview]
Message-ID: <20110908092633.2fcc01d7.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <CAFPAmTTaq2Lz=eGgfG2-5U0M9aS_aZLNAANAVPZj6TEo9EdjGg@mail.gmail.com>
On Mon, 5 Sep 2011 14:44:43 +0530
"kautuk.c @samsung.com" <consul.kautuk@gmail.com> wrote:
> Hi,
>
> I am aware that mlocked pages can be stopped from being reclaimed
> through the PFRA.
>
> However, is there any method to stop reclamation of the page-cache
> pages pertaining to
> a single file's inode without mlocking ?
>
> If I want to only use the open, read and write system calls and I want
> to set specific file cache
> pages to "non-reclaimable", how can I do so ?
>
For this kind of question, you should explain why you can't use mlock.
> Will the POSIX_FADV_WILLNEED option to the fadvise() system call solve
> this problem ?
>
I think no.
Thanks,
-Kame
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-09-08 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 9:14 kautuk.c @samsung.com
2011-09-08 0:26 ` KAMEZAWA Hiroyuki [this message]
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=20110908092633.2fcc01d7.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=consul.kautuk@gmail.com \
--cc=linux-fsdev@vger.rutgers.edu \
--cc=linux-fsdevel@vger.kernel.org \
--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