linux-kernel - Re: Zram for FreeBSD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3D1127B8-789C-4276-803E-49E10D2C4280@juniper.net>
Date:   Fri, 7 Oct 2016 17:30:01 +0000
From:   Cory Pruce <cpruce@...iper.net>
To:     Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
CC:     Nitin Gupta <nitingupta910@...il.com>,
        "minchan@...nel.org" <minchan@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Zram for FreeBSD

Cool, I am starting to get a good grasp on what is going on (I’ll probably need to use FreeBSD’s archive.h as opposed to Linux’s crypto.h). I am trying to get a hold on what exactly I need to port to FreeBSD. I see that (as Nitin suggested) zsmalloc is the main brains of handling the objects and that it creates a fixed amount of sharded “pages” which a compressed (or uncompressed) actual page can span. I see also that that depends on zpool. 

I will probably find all “dependencies”; however, if one of you could describe the components used/implemented for this, that’d be awesome. Also, any linux specific setup/layout details come to mind?

Seriously, any details would be appreciated. It will save me time.

Thanks,
Cory

On 10/5/16, 9:43 PM, "Sergey Senozhatsky" <sergey.senozhatsky.work@...il.com> wrote:

    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