From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] cfs, aan and network recommendations
Date: Wed, 17 Nov 2021 02:51:21 +0100 [thread overview]
Message-ID: <CAFSF3XPMwy9mkXWOLOgjnnftZXUorN8o=8bC8_3GzVBsi7NFsg@mail.gmail.com> (raw)
In-Reply-To: <78C6E67A-62A4-4F5E-B79E-6EF33F2A62B4@quintile.net>
thank you steve, this is a great summary and it explains everything
for me, didn't know it would check qid.version on every access!
On 11/16/21, Steve Simon <steve@quintile.net> wrote:
>
> cfs solves the problem of very low bandwidth links rather well (think
> modems) however it needs a low latency link so it can confirm qid.version on
> every file access.
>
> throughput issues can be mitigated for static filesystems, latency is the
> killer for 9p.
>
> -Steve
>
>
next prev parent reply other threads:[~2021-11-17 2:25 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 [this message]
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
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='CAFSF3XPMwy9mkXWOLOgjnnftZXUorN8o=8bC8_3GzVBsi7NFsg@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).