From: BenHanokh Gabriel <gabriel@SANgate.com>
To: Linux-MM mailing list <linux-mm@kvack.org>
Subject: purging file cache
Date: Thu, 24 Aug 2000 13:06:27 +0300 [thread overview]
Message-ID: <39A4F3A3.3030102@SANgate.com> (raw)
hi
i'm trying to find a way to purge file caching in a consistent way.
i found 2 relevant function
invalidate_inode_pages()
truncate_inode_pages()
does truncate_inode_pages() remove the page_cache only or that it
actually truncate the on-disk file?
can cache purging be done with a better granularity than the whole page,
some thing like purge_inode_cache( mapping, start, length ) ?
i don't realy understand the new VM model in linux 2.4 and what level of
consistancy exists between the page-cache and the file-buffers so i got
a few more questions:
can i invalidate cache for mmaped file? ( the reason i'm asking this is
that there is at least one os which doesn;t allow to purge cache from a
mmaped file )
can i invalidate mmaped section of a file which some process own a
READ-lock on it( so the next access to that section will cause
page-fault) or that this will break the mmap semantic ?
are files marked for mandatory locking protected from mmap access, or
that the file locks are checked only on the FS system_calls( read,
write...) ?
hope that at least some of those many questions will be answers
please CC me for any answer
--
regards
Benhanokh Gabriel
-----------------------------------------------------------------------------
"If you think C++ is not overly complicated, just what is a
protected abstract virtual base class with a pure virtual private
destructor,
and when was the last time you needed one?"
-- Tom Cargil, C++ Journal, Fall 1990. --
--
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-08-24 10:06 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=39A4F3A3.3030102@SANgate.com \
--to=gabriel@sangate.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