From: Roman Zippel <roman@augan.com>
To: linux-mm <linux-mm@kvack.org>
Subject: how does the fs cache work?
Date: Tue, 04 Jul 2000 13:15:37 +0200 [thread overview]
Message-ID: <3961C759.DA95744E@augan.com> (raw)
Hi,
I'm currently trying to understand how the fs cache in 2.4 works, but
I'm slightly confused, how a few things are supposed to work.
Am I seeing it correctly, that if we're looking for a free page we're
basically looking into three caches? We check for mapped pages
(swap_out), we shrink the lru_cache (shrink_mmap) and we clean the inode
cache (shrink_icache_memory).
Furthermore the only policy that I see that prevents a page being freed
is "was it used last time we checked?", how is that supposed to work
under load?
Is there any way to share a block that is read from a file and the same
read from the block device? A possible user might be e2fsck, but
currently it doesn't seem to be problem, as ext2 doesn't use the page
cache for meta data.
Hmm, I think, that's enough questions for now, I come up with more
later. :)
bye, Roman
--
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.eu.org/Linux-MM/
reply other threads:[~2000-07-04 11:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3961C759.DA95744E@augan.com \
--to=roman@augan.com \
--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