From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751970AbcJFEn1 (ORCPT ); Thu, 6 Oct 2016 00:43:27 -0400 Received: from mail-pa0-f46.google.com ([209.85.220.46]:33185 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750979AbcJFEnZ (ORCPT ); Thu, 6 Oct 2016 00:43:25 -0400 Date: Thu, 6 Oct 2016 13:43:21 +0900 From: Sergey Senozhatsky To: Cory Pruce Cc: Nitin Gupta , "sergey.senozhatsky.work@gmail.com" , "minchan@kernel.org" , linux-kernel@vger.kernel.org Subject: Re: Zram for FreeBSD Message-ID: <20161006044321.GC5458@swordfish> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On (10/05/16 16:47), Cory Pruce wrote: > Could one of you tell me why these compression algo’s were chosen, zram supports more than that. https://marc.info/?l=linux-kernel&m=146469777105130 > if they were implemented as a need for zram, and hm... not all of them (if any at all). lzo, *may be*, was motivated by "compression/decompression perfromance VS compression ratio", which is imporatant for zram. > what the policy is on porting these to FreeBSD? no idea. -ss