From: fgergo@gmail.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9p server to multiply 9p messages?
Date: Sun, 29 May 2022 13:41:47 +0200 [thread overview]
Message-ID: <CA+ctqrqjfVrdZ2-GjfkeWvhA-JtJb7YNqarwqs8KgvJ6CCxPfQ@mail.gmail.com> (raw)
In-Reply-To: <CA+ctqroT9VDBizz_nomiVMx5HWFNBrxJNdPRi0Jymy2qrx_TwQ@mail.gmail.com>
s/over 9p/higher than 9p/
On 5/29/22, fgergo@gmail.com <fgergo@gmail.com> wrote:
> As a first approximation - assuming identical namespaces - this
> multiplier 9p server (9plier? multi9plier?) could be trivially(?)
> useful, used with recover(4) on all connections and with an
> independent synchronization mechanism, in case states would fall out
> of sync.
>
> Furthermore I would not rule out usefulness if the namespaces are not
> identical, though I think a higher level model (over 9p) would need to
> be considered to built anything useful.
> Thanks for your insight!
>
> On 5/28/22, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
>> Interesting idea!
>>
>> This assumes the downstream servers have identical namespace hierarchy;
>> right?
>>
>> State management could be messy or impossible unless some sort of
>> transaction structure is imposed on the {walk, [open/create,
>> read/write]|[stat/wstat], clunk} sequences, where the server that
>> replies to walk first, gets that transaction.
>>
>> On Sat, May 28, 2022 at 9:04 AM <fgergo@gmail.com> wrote:
>>>
>>> Has anybody considered (or maybe even implemented) a 9p server to
>>> multiply incoming 9p messages to 2 or more 9p servers?
>>> Maybe with 2 different strategies for responding to the original
>>> request?
>>> 1. respond as soon as at least 1 response from one of the 9p servers
>>> is received,
>>> 2. respond only after all responses had been received.
>>> thanks!
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T769854fafd2b7d35-M176ab7d3e0344d1d02e485e3
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-05-29 11:42 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 [this message]
2022-05-29 23:16 ` Bakul Shah
2022-05-30 4:59 ` ori
2022-05-30 7:19 ` Bakul Shah
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=CA+ctqrqjfVrdZ2-GjfkeWvhA-JtJb7YNqarwqs8KgvJ6CCxPfQ@mail.gmail.com \
--to=fgergo@gmail.com \
--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).