From: G. David Butler gdb@dbSystems.com
Subject: [9fans] cfs type caching in the mnt driver
Date: Wed, 30 Jul 1997 10:44:43 -0500 [thread overview]
Message-ID: <19970730154443.vq-D9R_HSFGBfy6YsWd10SC8JpJO9X1SvgZ8i33gDvc@z> (raw)
I was looking around the cfs code and thought that it
may be interesting to hook the #M mnt device to the
vm system and have it cache data in unused memory.
Memory used by the cache would considered free by the
vm system so processes have first dibs.
This seems the best place to put this kind of caching
since it is where calls get converted to messages and
multiplexing here will allow the cache to be shared
by all processes.
Comments?
David Butler
gdb@dbSystems.com
next reply other threads:[~1997-07-30 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-30 15:44 G.David [this message]
1997-07-30 17:02 philw
1997-07-30 21:19 Frank
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=19970730154443.vq-D9R_HSFGBfy6YsWd10SC8JpJO9X1SvgZ8i33gDvc@z \
--to=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).