From: "Joe S" <joe@lifesoftserv.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Dual dialing/forking sessions to increase 9P throughput
Date: Mon, 4 Jan 2021 22:41:15 -0500 [thread overview]
Message-ID: <16098180750.51d0c6.72632@composer.9fans.topicbox.com> (raw)
In-Reply-To: <86tus46ujm.fsf@cmarib.ramside>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
hiro:
The purpose of doing this was not to just access multiple parts of the file. I was working off the quote below. Maybe a file server thats purpose is to mux parts of another file sounded like fun. My thoughts are that you could then transer thoes chunks on a single destination on seperate connections.
eg.
% mux -C 3 -F large.file
% tree.
├── large.file
└── large.file.mux
├── 1
├── 2
└── 3
1 directory, 4 files
Like I said though still learning though.
On Wednesday, 30 December 2020, at 12:20 AM, cigar562hfsp952fans wrote:
> There is, however, a very simple reason why this approach won't really
work: the fids for a file opened on one connection won't be recognized
by the server on the other connection.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te69bb0fce0f0ffaf-Mb319f4f5aae92c0b9de48f76
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2188 bytes --]
next prev parent reply other threads:[~2021-01-05 3:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 23:50 cigar562hfsp952fans
2020-12-30 8:12 ` [9fans] " joey
2021-01-03 23:51 ` [9fans] " Ethan Gardener
2021-01-04 10:55 ` Ole-Hjalmar Kristensen
2021-01-04 11:03 ` hiro
2021-01-04 19:08 ` joe
2021-01-04 20:44 ` hiro
2021-01-04 21:01 ` ori
2021-01-05 3:41 ` Joe S [this message]
2021-01-05 9:40 ` hiro
2021-01-06 22:21 ` [9fans] " cigar562hfsp952fans
2021-01-07 8:06 ` hiro
2021-01-07 16:02 ` [9fans] " ori
2021-01-25 22:31 ` David Arroyo
2021-01-27 16:25 ` Ethan Gardener
2021-01-27 16:52 ` ori
2021-01-27 17:34 ` Charles Forsyth
2021-01-28 0:17 ` David Arroyo
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=16098180750.51d0c6.72632@composer.9fans.topicbox.com \
--to=joe@lifesoftserv.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).