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]
Date:	Tue, 08 Feb 2011 21:32:16 -0500
From:	Nitin Gupta <ngupta@...are.org>
To:	Dan Magenheimer <dan.magenheimer@...cle.com>
CC:	gregkh@...e.de, Chris Mason <chris.mason@...cle.com>,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	matthew@....cx, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	jeremy@...p.org, Kurt Hackel <kurt.hackel@...cle.com>,
	npiggin@...nel.dk, riel@...hat.com,
	Konrad Wilk <konrad.wilk@...cle.com>, mel@....ul.ie,
	minchan.kim@...il.com, kosaki.motohiro@...fujitsu.com,
	sfr@...b.auug.org.au, wfg@...l.ustc.edu.cn, tytso@....edu,
	viro@...IV.linux.org.uk, hughd@...gle.com, hannes@...xchg.org,
	Matt <jackdachef@...il.com>
Subject: Re: [PATCH V2 0/3] drivers/staging: zcache: dynamic page cache/swap
 compression

On 02/08/2011 08:03 PM, Dan Magenheimer wrote:
>> (Historical note: This "new" zcache patchset supercedes both the
>> kztmem patchset and the "old" zcache patchset as described in:
>> http://lkml.org/lkml/2011/2/5/148)
>
> (In order to move discussion from the old kztmem patchset to
> the new zcache patchset, I am replying here to Matt's email
> sent at: https://lkml.org/lkml/2011/2/4/199 )
>
>> From: Matt [mailto:jackdachef@...il.com]
>
<snip>

>
>> • Coming back to usage of compcache - how about the problem of 60%
>> memory fragmentation (according to compcache/zcache wiki,
>> http://code.google.com/p/compcache/wiki/Fragmentation) ?
>> Could the situation be improved with in-kernel "memory compaction" ?
>> I'm not a developer so I don't know exactly how lumpy reclaim/memory
>> compaction and xvmalloc would interact with each other
>
> Nitin is the expert on compcache and xvmalloc, so I will leave
> this question unanswered for now.
>


I'm currently in the process of designing a new allocator that gives 
predictable memory fragmentation guarantees (at the expense of extra CPU 
cycles). I've not yet posted details anywhere but many of the ideas are 
from the "Compact Fit" allocator: 
http://www.usenix.org/event/usenix08/tech/full_papers/craciunas/craciunas_html/

I'm not sure how much time it will take since I'm not yet done with some 
of the design details, and then userspace implementation, testing, 
profiling and finally kernel port. Add to that extra concurrency issues 
when integrating with zcache!

Thanks,
Nitin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ