From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 26942 invoked from network); 4 Jan 2021 19:08:56 -0000 Received: from tb-ob1.topicbox.com (64.147.108.173) by inbox.vuxu.org with ESMTPUTF8; 4 Jan 2021 19:08:56 -0000 Received: from tb-mx1.topicbox.com (tb-mx1.nyi.icgroup.com [10.90.30.61]) by tb-ob1.topicbox.com (Postfix) with ESMTP id A994E36855 for ; Mon, 4 Jan 2021 14:08:51 -0500 (EST) (envelope-from bounce.mMb8a0447d7180b423909022ff.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx1.topicbox.com (Postfix, from userid 1132) id B0629102F86F; Mon, 4 Jan 2021 14:08:51 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=9fans.net; h=from:to :subject:message-id:references:in-reply-to:date:mime-version :content-type:content-transfer-encoding:list-help:list-id :list-post:list-subscribe:reply-to:list-unsubscribe; s=dkim-1; bh=LGQjKv9zpytMH4J7FXVlRI/fR3ucJ15+Lnols8Pz6ek=; b=AkEc9fLeqMNX euuUEt933lhSQ8Jv58T2KPw7hr5C+rSmSZGZR6N2CGlNtSgW0NkjDqCNZZ2bv0Sf 6qBFgN5gSmUHwpxhvhYgO0mGbijUXaudTWT+Or1zGs03FWy7iPRcrgg+dWEzg1gy h1oyIvn9o/OOK++F2kt/4jTw39TFeV4= From: joe@lifesoftserv.com To: 9fans <9fans@9fans.net> Subject: Re: [9fans] Dual dialing/forking sessions to increase 9P throughput Message-Id: <16097873250.ffaB33.87073@composer.9fans.topicbox.com> References: <86tus46ujm.fsf@cmarib.ramside> <3e07aed0-6865-460a-9433-826cf173bb85@www.fastmail.com> In-Reply-To: Date: Mon, 4 Jan 2021 14:08:45 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="16097873251.561A5CcCA.87073" Content-Transfer-Encoding: 7bit Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 44584248-4ec0-11eb-b530-11b39134e1fa Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UZTY5YmIwZmNlMGYwZmZhZi1NYjhhMDQ0N2Q3MTgwYjQyMzkwOTAy?= =?UTF-8?B?MmZmPg==?= List-Help: List-Id: "9fans" <9fans.9fans.net> List-Post: List-Software: Topicbox v0 List-Subscribe: Precedence: list Reply-To: 9fans <9fans@9fans.net> List-Unsubscribe: , Topicbox-Delivery-ID: 2:9fans:437d30aa-c441-11e9-8a57-d036212d11b0:522be890-2105-11eb-b15e-8d699134e1fa:Mb8a0447d7180b423909022ff:1:MwBmN49SHGQBCBTa7R5qoqpc2LHZZBNkbOEH6-WVb7Y --16097873251.561A5CcCA.87073 Date: Mon, 4 Jan 2021 14:08:45 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Might be more than it is worth but what if you made a small program/file se= rver that addressed portions of the "larger" file as their own file in a te= mporary directory. On write you would have to preallocate the file on the d= isk and write eatch section to it's respective range. "Chunks" would be sim= plified 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. Ev= erything 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 wor= k. Just a thought. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te69bb0fce0f0ffaf-Mb8a04= 47d7180b423909022ff Delivery options: https://9fans.topicbox.com/groups/9fans/subscription --16097873251.561A5CcCA.87073 Date: Mon, 4 Jan 2021 14:08:45 -0500 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Might be more than it is worth but what if you= made a small program/file server that addressed portions of the "larg= er" file as their own file in a temporary directory. On write you woul= d have to preallocate the file on the disk and write eatch section to it= 9;s respective range. "Chunks" would be simplified by having a pr= e-copy size and a "Chunk number" appended on the end of each chun= k. 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&qu= ot; program to copy from source to destination. Getting better with plan9 b= ut not enough so to implement something like this or know if it would work.= Just a thought.
= --16097873251.561A5CcCA.87073--