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/19cb61337bab7b4de856fcbf29b55965647be091,
similar in spirit to your idea.
The core idea was
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
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
