From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 9 06:30:41 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC1381019 for ; Tue, 9 Oct 2012 06:30:41 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id 296758FC19 for ; Tue, 9 Oct 2012 06:30:40 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q996R9CM013488; Tue, 9 Oct 2012 08:27:09 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q996R9XU013485; Tue, 9 Oct 2012 08:27:09 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Tue, 9 Oct 2012 08:27:09 +0200 (CEST) From: Wojciech Puchar To: Peter Pentchev Subject: Re: SMP Version of tar In-Reply-To: <20121008083814.GA5830@straylight.m.ringlet.net> Message-ID: References: <5069C9FC.6020400@brandonfa.lk> <324B736D-8961-4E44-A212-2ECF3E60F2A0@kientzle.com> <20121008083814.GA5830@straylight.m.ringlet.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Tue, 09 Oct 2012 08:27:10 +0200 (CEST) Cc: freebsd-hackers@freebsd.org, Brandon Falk X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 06:30:42 -0000 > Not necessarily. If I understand correctly what Tim means, he's talking > about an in-memory compression of several blocks by several separate > threads, and then - after all the threads have compressed their > respective blocks - writing out the result to the output file in order. > Of course, this would incur a small penalty in that the dictionary would > not be reused between blocks, but it might still be worth it. all fine. i just wanted to point out that ungzipping normal standard gzip file cannot be multithreaded, and multithreaded-compressed gzip output would be different.