Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2695CDD48 for ; Wed, 1 Aug 2012 21:54:04 +0000 (UTC) Received: (qmail 53764 invoked by uid 500); 1 Aug 2012 21:54:03 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 53727 invoked by uid 500); 1 Aug 2012 21:54:03 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 53713 invoked by uid 99); 1 Aug 2012 21:54:03 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 21:54:03 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id AEF7A14052C for ; Wed, 1 Aug 2012 21:54:03 +0000 (UTC) Date: Wed, 1 Aug 2012 21:54:03 +0000 (UTC) From: "Tim Broberg (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <256079052.2465.1343858043718.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1212380010.35736.1331148658543.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-8148) Zero-copy ByteBuffer-based compressor / decompressor API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426942#comment-13426942 ] Tim Broberg commented on HADOOP-8148: ------------------------------------- Regrettably, Exar has closed the San Diego office before I could complete this task. My replacement will continue my efforts, but will likely have his hands full coming up to speed. I have implemented the patch for our own codec, but we will not be providing a Snappy version any time soon. Apologies for leaving the work half done, - Tim. > Zero-copy ByteBuffer-based compressor / decompressor API > -------------------------------------------------------- > > Key: HADOOP-8148 > URL: https://issues.apache.org/jira/browse/HADOOP-8148 > Project: Hadoop Common > Issue Type: New Feature > Components: io, performance > Reporter: Tim Broberg > Assignee: Tim Broberg > Attachments: hadoop-8148.patch, hadoop8148.patch, zerocopyifc.tgz > > > Per Todd Lipcon's comment in HDFS-2834, " > Whenever a native decompression codec is being used, ... we generally have the following copies: > 1) Socket -> DirectByteBuffer (in SocketChannel implementation) > 2) DirectByteBuffer -> byte[] (in SocketInputStream) > 3) byte[] -> Native buffer (set up for decompression) > 4*) decompression to a different native buffer (not really a copy - decompression necessarily rewrites) > 5) native buffer -> byte[] > with the proposed improvement we can hopefully eliminate #2,#3 for all applications, and #2,#3,and #5 for libhdfs. > " > The interfaces in the attached patch attempt to address: > A - Compression and decompression based on ByteBuffers (HDFS-2834) > B - Zero-copy compression and decompression (HDFS-3051) > C - Provide the caller a way to know how the max space required to hold compressed output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira