linux-kernel - Re: [PATCH] z3fold: the 3-fold allocator for compressed pages

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAMJBoFNQtwSRoz12qHnjX=E7evEaJC5CQbYE68cH9qTS2MZqQQ@mail.gmail.com>
Date:	Thu, 14 Apr 2016 19:45:49 +0200
From:	Vitaly Wool <vitalywool@...il.com>
To:	Seth Jennings <sjenning@...hat.com>
Cc:	Vlastimil Babka <vbabka@...e.cz>, Linux-MM <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dan Streetman <ddstreet@...e.org>
Subject: Re: [PATCH] z3fold: the 3-fold allocator for compressed pages

On Thu, Apr 14, 2016 at 5:53 PM, Seth Jennings <sjenning@...hat.com> wrote:
> On Thu, Apr 14, 2016 at 4:06 AM, Vitaly Wool <vitalywool@...il.com> wrote:
>>
>>
>> On Thu, Apr 14, 2016 at 10:48 AM, Vlastimil Babka <vbabka@...e.cz> wrote:
>>>
>>> On 04/14/2016 10:05 AM, Vitaly Wool wrote:
>>>>
>>>> This patch introduces z3fold, a special purpose allocator for storing
>>>> compressed pages. It is designed to store up to three compressed pages
>>>> per
>>>> physical page. It is a ZBUD derivative which allows for higher
>>>> compression
>>>> ratio keeping the simplicity and determinism of its predecessor.
>>>
>>>
>>> So the obvious question is, why a separate allocator and not extend zbud?
>>
>>
>> Well, as far as I recall Seth was very much for keeping zbud as simple as
>> possible. I am fine either way but if we have zpool API, why not have
>> another zpool API user?
>>
>>>
>>> I didn't study the code, nor notice a design/algorithm overview doc, but
>>> it seems z3fold keeps the idea of one compressed page at the beginning, one
>>> at the end of page frame, but it adds another one in the middle? Also how is
>>> the buddy-matching done?
>
> Yes, as soon as you introduce a 3rd object in the page, zpage
> fragmentation becomes an issue.  Having a middle object partitions
> that zpage, blocking allocations that are larger than either
> partition, even though the combined size of the partitions could have
> accommodated the object.

Yes, but this situation is easy to track down and work around by
moving the middle object to either the beginning or the end. In case
of the current implementation it is the beginning.

> This also means that the unbuddied list is broken in this
> implementation.  num_free_chunks() is calculating the _total_ free
> space in the page.  But that is not that the _usable_ free space by a
> single object, if the middle object has partitioned that free space.

Once again, there is the code in z3fold_free() that makes sure the
free space within the page is contiguous so I don't think the
unbuddied list is, or will be, broken.

~vitaly