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 o
Thanks yes, this would be one use-case.
On 5/28/22, ron minnich wrote:
> not for 9p, but in 1993, when Gene Kim interned with me at the
> Supercomputing Research Center, we did this:
> https://www.semanticscholar.org/paper/Bigfoot-NFS-%3A-A-Parallel-File-Striping-NFS-Server-(-Kim/19cb61337bab7b4d
s/over 9p/higher than 9p/
On 5/29/22, fge...@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
On May 28, 2022, at 9:02 AM, fge...@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 respons
Quoth Bakul Shah :
>
> Some variation of this would be interesting for a clustered
> or distributed filesystem. The challenge would be doing this
> in an understandable way, cleanly and with good performance.
> Probably using separate namespaces for control & management
> operations.
the challeng
