From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Dual dialing/forking sessions to increase 9P throughput
Date: Mon, 4 Jan 2021 12:03:06 +0100 [thread overview]
Message-ID: <CAFSF3XNic0mzonVcG=yhLnaS6-NfCYmrSSc_PFBmWdHZXmrGVA@mail.gmail.com> (raw)
In-Reply-To: <CAHqDL_-T8yGoF8FaMDjwRQ+SyNbdy1FPxGRN4RLcWD+BJN71Gg@mail.gmail.com>
reliability can be provided by AAN, already.
You can try out the Op protocol for inferno though, if you want to see
a working implementation of streaming 9p.
I've been running it for a long time and it worked perfectly for my use case.
On 1/4/21, Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com> wrote:
> I agree with you that using the existing tag mechanism to keep multiple
> requests in flight should be sufficient. I get the impression that this is
> not readily supported by the higher level libraries, though.
>
> As an aside, I seem to remember that John Floren sugegsed (and implemented)
> changes to the 9P protocol making it more suitable for streaming media by
> creating another TCP connection on the side.
>
> On Mon, Jan 4, 2021 at 12:52 AM Ethan Gardener <eekee57@fastmail.fm> wrote:
>
>> > The idea, basically, is to use an open flag (OJUMBO) to signal that two
>> > connections to the same server should be attempted.
>>
>> What's the advantage over fcp(1)? 9p can have numerous requests "in
>> flight" at once to work around latency issues, but of all the user
>> programs, fcp is probably the only one which takes advantage of this.
>>
>> > If a second
>> > connection can be established, it is used for normal 9P transactions,
>> > while the first connection is used for large ("jumbo") writes.
>>
>> How large is "jumbo"? I believe all the user programs have 8KB buffers at
>> present; are you going to change them all?
>>
>> I'm not negative about this; just raising the points.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te69bb0fce0f0ffaf-M6f610222b3d7fc1800e82174
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-01-04 11:03 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 [this message]
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
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='CAFSF3XNic0mzonVcG=yhLnaS6-NfCYmrSSc_PFBmWdHZXmrGVA@mail.gmail.com' \
--to=23hiro@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).