From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] Dual dialing/forking sessions to increase 9P throughput
Date: Mon, 04 Jan 2021 13:01:10 -0800 [thread overview]
Message-ID: <5F1E999F6F9693394A6403768C266D22@eigenstate.org> (raw)
In-Reply-To: <16097873250.ffaB33.87073@composer.9fans.topicbox.com>
Quoth joe@lifesoftserv.com:
> Might be more than it is worth but what if you made a small
> program/file server that addressed portions of the "larger" file as
> their own file in a temporary directory. On write you would have to
> preallocate the file on the disk and write eatch section to it's
> respective range. "Chunks" would be simplified by having a pre-copy
> size and a "Chunk number" appended on the end of each chunk. Used to
> write to the correct location in the destination. Everything in else
> could remain the same. You would just use the "Split/Bulk Copy"
> program to copy from source to destination. Getting better with plan9
> but not enough so to implement something like this or know if it would
> work. Just a thought.
http://man.9front.org/4/cfs
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te69bb0fce0f0ffaf-Mf9a01546241ea2a6777788c1
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-01-04 21:01 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 [this message]
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=5F1E999F6F9693394A6403768C266D22@eigenstate.org \
--to=ori@eigenstate.org \
--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).