mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Xin Zhao" <uszhaoxin@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Can someone explain under what condition inode cache pages can be swapped out?
Date: Thu, 3 Aug 2006 02:15:01 -0400	[thread overview]
Message-ID: <4ae3c140608022315y675eed20hcefbb8fb0407f4a3@mail.gmail.com> (raw)

Specifically, how a swaping system determine which page should be
swapped out when memory is tight? Intuitively, I think inode cache
pages should be swapped out as late as possible. But how Linux mkae
decision on this? Why linux does not pin inode pages in the memory?

Thanks in advance for kind help!

xin

             reply	other threads:[~2006-08-03  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  6:15 Xin Zhao [this message]
2006-08-03  7:55 ` Jan Engelhardt
2006-08-03 15:32   ` Xin Zhao
2006-08-04  5:58     ` Jan Engelhardt
2006-08-04 14:44       ` Al Boldi

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=4ae3c140608022315y675eed20hcefbb8fb0407f4a3@mail.gmail.com \
    --to=uszhaoxin@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®