From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Cory Pruce <cpruce@juniper.net>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Nitin Gupta <nitingupta910@gmail.com>,
"minchan@kernel.org" <minchan@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Zram for FreeBSD
Date: Mon, 10 Oct 2016 15:44:04 +0900 [thread overview]
Message-ID: <20161010064404.GA488@swordfish> (raw)
In-Reply-To: <3D1127B8-789C-4276-803E-49E10D2C4280@juniper.net>
On (10/07/16 17:30), Cory Pruce wrote:
> 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.
zsmalloc doesn't depend on zpool. zpool is an abstraction layer used
by zswap.
> 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?
there is a whole bunch of hacks that Nitin, Minchan and others used
in zsmalloc() to minimize its space consumption (struct page fields
re-usage, etc). comments in zsmalloc() can shed some light.
-ss
next prev parent reply other threads:[~2016-10-10 6:44 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 ` Zram for FreeBSD Sergey Senozhatsky
2016-10-07 17:30 ` Cory Pruce
2016-10-10 6:44 ` Sergey Senozhatsky [this message]
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=20161010064404.GA488@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.