9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: Dual dialing/forking sessions to increase 9P throughput
Date: Thu, 7 Jan 2021 09:06:22 +0100	[thread overview]
Message-ID: <CAFSF3XNigZjgkJTYLh1n0oaHsZMo5=6VG2J6sjL=BpNGBHHSVA@mail.gmail.com> (raw)
In-Reply-To: <868s95g0zy.fsf@cmarib.ramside>

> The problem is that throughput and responsiveness are enemies.
no. not throughput, but buffer sizes are the enemy of latency

> you're trying to push a large quantity of data down a TCP connection,
> and try to do anything interactive over that same connection, the
> latency will make that interaction very slow

no. you have full freedom to prioritize the interactive part on
application layer (since you mention TCP layer).

> the transport medium needs to know how to differentiate
> between the two kinds of traffic.
no, any other layer could also differentiate the traffic.

> you would need a way to set different TCP options on 9P messages for different purposes.

TCP doesn't differentiate well. TCP fairness is not fine-grained
enough for this, so i still don't think the transport layer is well
suited.

what we really need is 9p (file/fd) level distributed scheduling.

>
> "Joe S" <joe@lifesoftserv.com> writes:
>
>> 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.
> 
> I might be possible to create a file server which interposes itself
> between a 9P client and 9P server and bonds multiple network connections
> together into a single 9P session.  It would be sort of a userspace
> replacement for the kernel's mount driver.  Wait a minute, this problem
> can be solved with a filesystem?  Of course... I should have thought of
> that.  ;)

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te69bb0fce0f0ffaf-M8679a1e06d55c6877dbfbdfe
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2021-01-07  8:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 23:50 [9fans] " 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
2021-01-05  9:40   ` hiro
2021-01-06 22:21   ` [9fans] " cigar562hfsp952fans
2021-01-07  8:06     ` hiro [this message]
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='CAFSF3XNigZjgkJTYLh1n0oaHsZMo5=6VG2J6sjL=BpNGBHHSVA@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).