Re: Swap Compression
jw schultz (email@example.com)
Thu, 1 May 2003 19:46:13 -0700
On Thu, May 01, 2003 at 06:07:59PM -0400, rmoser wrote:
> Had a thought. Why wait for a compression algorithm? Jorn, if you are going
> to work on putting the code into the kernel and making the stuff to allow the
> swap code to use it, why not start coding it before the compression code is
> finished? i.e. get the stuff down for the swap filtering (filtering i.e. passing
> through a compression or encryption routine) and swap-on-ram stuff, and later
> take the compression algo code and place the module interface on it and make
> a kernel module.
> At this point, I'd say to allow specified order filters, to allow for swap cyphering
> and compression. Security, you know; swap files are a security hazard. Just
> power-off, boot a root disk, pull up the swap partition, rip out the blocks, and
> look for what looks to be the root password.
While we're having thoughts, this thread keeps me thinking
it would make sense to have a block device driver that would
be assigned unused memory.
I don't mean memory on video cards etc. I'm thinking of the
10% of RAM unused when 1GB systems are booted with MEM=900M
because they run faster with HIGHMEM turned off.
The primary use for this "device" would be high priority swap.
Even with whatever overhead it takes to access it should be
orders of magnitude faster than any spinning media.
J.W. Schultz Pegasystems Technologies
email address: firstname.lastname@example.org
Remember Cernan and Schmitt
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/