All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Cory Pruce <cpruce@juniper.net>
Cc: Nitin Gupta <nitingupta910@gmail.com>,
	"sergey.senozhatsky.work@gmail.com" 
	<sergey.senozhatsky.work@gmail.com>,
	"minchan@kernel.org" <minchan@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Zram for FreeBSD
Date: Thu, 6 Oct 2016 13:43:21 +0900	[thread overview]
Message-ID: <20161006044321.GC5458@swordfish> (raw)
In-Reply-To: <BFFB31F3-F514-453D-AEE5-D1506109CB77@juniper.net>

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

       reply	other threads:[~2016-10-06  4:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FDF35643-03BA-48FE-8CD5-DA6E715875C4@juniper.net>
     [not found] ` <BD391BEE-37F1-4048-A48F-248D35245581@juniper.net>
     [not found]   ` <CAAdovdkndkBoX3jQiUA1YZgjOyixiBSfoPOWW39zxDt0tP_-=w@mail.gmail.com>
     [not found]     ` <BFFB31F3-F514-453D-AEE5-D1506109CB77@juniper.net>
2016-10-06  4:43       ` Sergey Senozhatsky [this message]
2016-10-07 17:30         ` Zram for FreeBSD Cory Pruce
2016-10-10  6:44           ` Sergey Senozhatsky
2016-10-10  6:55             ` Sergey Senozhatsky
2016-10-11 16:47               ` Cory Pruce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161006044321.GC5458@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=cpruce@juniper.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=nitingupta910@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.