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:	Sat, 21 Mar 2009 18:01:40 +0530
From:	Nitin Gupta <nitingupta910@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Pekka Enberg <penberg@...helsinki.fi>,
	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] compcache documentation

Andrew Morton wrote:
> On Fri, 20 Mar 2009 19:44:08 +0530 Nitin Gupta <ngupta@...are.org> wrote:
> 
>> ...
>>
>> +   backing_dev: This is block device to be used as backing store for compcache.
>> +	It must be a valid swap partition. We move data to this device when we
>> +	encounter incompressible page or memlimit is reached. TODO: we may also
>> +	move some pages from compcache to this device in case system is really
>> +	low on memory.
>> +	This device is not directly visible to kernel as a swap device
>> +	(/proc/swaps will only show /dev/ramzswap0 and not this device).
>> +	Managing this backing device is the job of compcache module.
> 
> hrm, OK, it kinda/sorta/maybe might be a little bit like a "compressed
> cache".  But if someone comes up with a real compressed cache (ie:
> pagecache) then they'll want their name back.
> 
Rename is in progress: compcache->ramzswap :)

> Also, the kernel already has a widespread and well-established "backing
> device" concept, in include/linux/backing-dev.h.  This new feature's
> poaching of that identifier is a bit confusing.  It would be nice to do a
> wholesale rename if possible.  secondary_dev?  nv_dev?
> 

backing_swap?

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