9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] cfs, aan and network recommendations
Date: Wed, 17 Nov 2021 22:52:44 +0000	[thread overview]
Message-ID: <42A18576-7070-4E51-A6E8-BA05F7EC3BD1@quintile.net> (raw)
In-Reply-To: <CAFSF3XPUCzSFNMoWP4DtQVPqrFj2DpWpEPV8eRuDWx4B7r+6Zw@mail.gmail.com>


cfs could be modified, you could relax the rules…

for example if you know your files are readonly you only need to do a dirread, no subsequent checks.

if the path matches /*/bin/* assume the version is up to date (bin dires are fairly static)

you could keep a timestamp when the version was last checked if the file has not changed for (say) a week then its version only needs to be validated (say) once a day.

if you have recently fetched the versions on the path /sys/src/9/pc dont check them again until (say) 5 mins have elapsed.

the other approach suggested by nemo was to extend 9p with streaming apis - readfile and writefile. these would allow a complete file to be read with only 1 rtt rather than an rtt per path component, 1 for walk, open, and close, and 1 for each 8k of data.

all of these have disadvantages but in real use they could make life easier woth a remote fs.

-Steve


      reply	other threads:[~2021-11-17 22:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 22:39 sirjofri
2021-11-16  4:12 ` Xiao-Yong Jin
2021-11-16 18:18   ` Noam Preil
2021-11-16 19:04     ` Steve Simon
2021-11-17  1:51       ` hiro
2021-11-17  7:31         ` sirjofri
2021-11-17  9:45           ` hiro
2021-11-17 10:31             ` sirjofri
2021-11-17 15:31               ` hiro
2021-11-18 22:05                 ` Steve Simon
2021-11-18 23:21                   ` hiro
2021-11-17 21:35               ` sirjofri
2021-11-17 22:12                 ` hiro
2021-11-17 22:52                   ` Steve Simon [this message]

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=42A18576-7070-4E51-A6E8-BA05F7EC3BD1@quintile.net \
    --to=steve@quintile.net \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).