From: Bakul Shah <bakul@iitbombay.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9p server to multiply 9p messages?
Date: Mon, 30 May 2022 00:19:46 -0700 [thread overview]
Message-ID: <548D3C1F-DFCC-4DCE-AB37-3CA48997AE69@iitbombay.org> (raw)
In-Reply-To: <AC0D3717011B2BD6C0606D9B5AB748DB@eigenstate.org>
On May 29, 2022, at 10:01 PM, ori@eigenstate.org wrote:
>
> the challenge is that 9p is stateful, so all servers must
> replay the same messages in the same order; this means that
> if one of the replicas fails or returns a result that is not
> the same as the other, the front falls off.
>
> this means mirroring messages naïvely reduces reliability
> and performance, rather than increasing it.
I was not thinking of mirroring.
I was thinking of ckustered or distributed systems like
CephFS, IPFS, GlusterFS etc but thinking a cleaner &
simpler design might be possible. But it is quite possible
my brainstorm/pipedream is not realistic!
9p itself is low performance but that is a separate issue.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T769854fafd2b7d35-M356e62122d1f1d87bf554dca
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-05-30 7:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 16:02 fgergo
2022-05-28 18:43 ` Skip Tavakkolian
2022-05-28 19:21 ` ron minnich
2022-05-29 10:33 ` fgergo
2022-05-29 10:23 ` fgergo
2022-05-29 11:41 ` fgergo
2022-05-29 23:16 ` Bakul Shah
2022-05-30 4:59 ` ori
2022-05-30 7:19 ` Bakul Shah [this message]
2022-05-30 8:03 ` fgergo
2022-05-30 8:35 ` hiro
2022-05-31 16:14 ` ron minnich
2022-05-31 18:27 ` hiro
2022-05-31 18:35 ` ori
2022-06-01 12:00 ` ron minnich
2022-06-01 14:51 ` ori
2022-06-01 15:31 ` hiro
2022-06-01 15:39 ` hiro
2022-06-01 16:01 ` ori
2022-06-01 4:26 ` Bakul Shah
2022-06-01 7:25 ` hiro
2022-06-01 15:55 ` Jacob Moody
2022-06-01 17:56 ` Steve Simon
2022-06-01 22:29 ` hiro
2022-05-30 8:33 ` hiro
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=548D3C1F-DFCC-4DCE-AB37-3CA48997AE69@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=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).