Awesome thanks Sergey. I’ll look through it soon :)
On 10/9/16, 11:55 PM, "Sergey Senozhatsky"
wrote:
>you'd also probably want to look at the older zsmalloc version
>(add compaction and migration later, if need be)
>
Awesome thanks Sergey. I’ll look through it soon :)
On 10/9/16, 11:55 PM, "Sergey Senozhatsky"
wrote:
>you'd also probably want to look at the older zsmalloc version
>(add compaction and migration later, if need be)
>
you'd also probably want to look at the older zsmalloc version
(add compaction and migration later, if need be)
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/mm/zsmalloc.c?id=refs/tags/v4.0
it used to be simpler back then.
-ss
you'd also probably want to look at the older zsmalloc version
(add compaction and migration later, if need be)
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/mm/zsmalloc.c?id=refs/tags/v4.0
it used to be simpler back then.
-ss
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
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
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
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
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=146469777105130
>if they were implemented as a need for zram, and
hm... not all of them (if any at all). lzo,
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=146469777105130
>if they were implemented as a need for zram, and
hm... not all of them (if any at all). lzo,
10 matches
Mail list logo