From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Persistent cache for cfs
Date: Fri, 18 May 2001 14:50:57 +0000 [thread overview]
Message-ID: <3B052A55.8EED5F17@null.net> (raw)
In-Reply-To: <3B042432.691F18B8@null.net>
"Douglas A. Gwyn" wrote:
> ... files have a new two-valued attribute, "temporary"
> or "permanent" ...
It occurs to me that this could be generalized to a
"priority level" treated uniformly by the caching
subsystem, with low-priority files more subject to
replacement in the cache. The cache "scheduler"
could also take into account access pattern (time
since last access or something more clever). One
could play with the cache scheduling algorithm
without massing with the filesystem representation
once the priority-level attribute existed.
next prev parent reply other threads:[~2001-05-18 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-12 13:02 presotto
2001-05-12 17:35 ` Fariborz 'Skip' Tavakkolian
2001-05-16 8:43 ` Matthew Weigel
2001-05-18 8:35 ` Douglas A. Gwyn
2001-05-18 14:50 ` Douglas A. Gwyn [this message]
2001-05-21 8:39 ` Matthew Weigel
2001-05-21 14:26 ` Ronald G Minnich
-- strict thread matches above, loose matches on Subject: below --
2001-05-12 4:26 Fariborz 'Skip' Tavakkolian
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=3B052A55.8EED5F17@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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).