linux-kernel - Re: [PATCH 0/3] zram: generic RAM based compressed R/W block devices

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: <4C006C11.7030309@vflare.org>
Date:	Sat, 29 May 2010 06:51:21 +0530
From:	Nitin Gupta <ngupta@...are.org>
To:	Greg KH <greg@...ah.com>
CC:	Pekka Enberg <penberg@...helsinki.fi>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Minchan Kim <minchan.kim@...il.com>,
	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	Cyp <cyp561@...il.com>, driverdev <devel@...verdev.osuosl.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] zram: generic RAM based compressed R/W block devices

On 05/28/2010 09:56 PM, Greg KH wrote:
> On Fri, May 28, 2010 at 09:38:53PM +0530, Nitin Gupta wrote:
>> Hi All,
>>
>> On 05/24/2010 07:48 PM, Nitin Gupta wrote:
>>> Creates RAM based block devices: /dev/zramX (X = 0, 1, ...).
>>> Pages written to these disks are compressed and stored in memory
>>> itself. These disks allow very fast I/O and compression provides
>>> good amounts of memory savings.
>>>
>>> This is enhancement over existing ramzswap driver which creates
>>> virtual block devices (/dev/ramzswapX) which could be used only
>>> as swap disks.
>>>
>>> Now, with the ability to handle any kind of I/O request, zram
>>> devices have lot more use cases:
>>>  - /tmp storage
>>>  - various caches under /var
>>>  - swap disks
>>>  - maybe even more! :)
>>>
>>> Performance numbers can be found at:
>>> http://code.google.com/p/compcache/wiki/zramperf
>>>
>>
>> Any reviews/comments, please?
> 
> We are all busy with the .35-rc1 merge work at the moment, sorry.
> 

Thanks for your reply.

Ok, in the meantime, I will further test it and keep building upon it.
When rc1 workload is over, I think all this can be merged in linux-next?

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/