Re: [hybi] frame length encoding

"Shelby Moore" <shelby@coolpage.com> Sat, 21 August 2010 20:56 UTC

Return-Path: <shelby@coolpage.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 957993A6910 for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 13:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.113
X-Spam-Level:
X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[AWL=0.486, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mLHQk1M5JldK for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 13:56:45 -0700 (PDT)
Received: from www5.webmail.pair.com (www5.webmail.pair.com [66.39.3.83]) by core3.amsl.com (Postfix) with SMTP id 9967E3A68CC for <hybi@ietf.org>; Sat, 21 Aug 2010 13:56:45 -0700 (PDT)
Received: (qmail 57091 invoked by uid 65534); 21 Aug 2010 20:57:19 -0000
Received: from 121.97.54.174 ([121.97.54.174]) (SquirrelMail authenticated user shelby@coolpage.com) by sm.webmail.pair.com with HTTP; Sat, 21 Aug 2010 16:57:19 -0400
Message-ID: <b09e8e740ef2b5b5ec3c85a5d9dcfd08.squirrel@sm.webmail.pair.com>
In-Reply-To: <1282423311.2014.6.camel@tng>
References: <AANLkTimKbmcpgx8k0uXUWvCO=8w9pPrtV=3y4qh6363k@mail.gmail.com> <alpine.DEB.2.00.1008212037190.27211@tvnag.unkk.fr> <AANLkTinrsT+wV48nHvVW_1ChGYffkq7jisU2-PZnMyKg@mail.gmail.com> <alpine.DEB.2.00.1008212123460.27211@tvnag.unkk.fr> <20ef7ed5e135c57c1ee5a741658b9d98.squirrel@sm.webmail.pair.com> <1282423311.2014.6.camel@tng>
Date: Sat, 21 Aug 2010 16:57:19 -0400
From: Shelby Moore <shelby@coolpage.com>
To: Patrick McManus <mcmanus@ducksong.com>
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] frame length encoding
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shelby@coolpage.com
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Aug 2010 20:56:46 -0000

> On Sat, 2010-08-21 at 15:54 -0400, Shelby Moore wrote:
>
>>
>> No because for any file on disk larger than 4GB, we will have to move
>> the
>> entire file through the CPU, when we wouldn't had to otherwise:
>>
>
> there seems to be a misunderstanding about ZC techniques here. To be
> efficient they certainly require a large-ish chunk size, but there is no
> all-or-nothing requirement like you assert that would require copying
> through the CPU to only send a subset of the data.
>
> 32 bits with chunking would be fine to accommodate zero copy.

My understanding is there would be copying, if you read my link again
carefully:

http://www.ietf.org/mail-archive/web/hybi/current/msg03402.html

The reason is because I understand from what I read at John's links that
the entire file is contiguous in memory (because it is a memory mapped or
memory cached copy of the file on the disk), and thus to insert the frame
headers at the 32bit chunks, you would have to move the entire file
through the CPU.  Is my understanding incorrect?  Can you simply rewrite
one sector on disk and the memory manager remaps?

>
> there are some folks that want to be able to send any message in one
> chunk for unrelated reasons.