From: Livio Baldini Soares <livio@ime.usp.br>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: rmoser <mlmoser@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: Re: Swap Compression
Date: Sun, 27 Apr 2003 16:57:31 -0300 [thread overview]
Message-ID: <20030427195731.GA5759@ime.usp.br> (raw)
In-Reply-To: <20030427190444.GC5174@wohnheim.fh-wedel.de>
Hello,
Unfortunately, I've missed the beginning of this discussion, but it
seems you're trying to do almost exactly what the "Compressed Cache"
project set out to do:
http://linuxcompressed.sourceforge.net/
_Please_ take a look at it. Rodrigo de Castro (the author) spent a
_lot_ of time working out the issues and corner details which a system
like this entail. I've been also involved in the project, even if not
actively coding, but giving suggestions and helping out when time
permitted. This project has been the core of his Master's
dissertation, which he has just finished writting recently, and will
soon defend.
It would be foolish (IMHO) to start from scratch. Take a look at the
web site. There is a nice sketch of the degin he has chosen here:
http://linuxcompressed.sourceforge.net/design/
Scott Kaplan, a researcher interested in compression of memory, has
also helped a bit. This article is something definitely worth reading,
and was one of Rodrigo's "starting point":
http://www.cs.amherst.edu/~sfkaplan/papers/compressed-caching.ps.gz
(There are other relevant sources available on the web page).
Rodrigo has also written a paper about his compressed caching which
has much more up-to-date information than the web page. His newest
benchmarks of the newest compressed cache version shows better
improvements then the numbers on the web page too. I'll ask him to put
it somewhere public, if he's willing.
Jörn Engel writes:
> On Sun, 27 April 2003 14:31:25 -0400, rmoser wrote:
[...]
> Another thing: Did you look at the links John Bradford gave yet? It
> doesn't hurt to try something alone first, but once you have a good
> idea about what the problem is and how you would solve it, look for
> existing code.
I think the compressed cache project is the one John mentioned.
> Most times, someone else already had the same idea and the same
> general solution. Good, less work. Sometimes you were stupid and the
> existing solution is much better. Good to know. And on very rare
> occasions, your solution is better, at least in some details.
>
> Well, in this case, the sourceforge project appears to be silent since
> half a year or so, whatever that means.
It means Rodrigo has been busy writting his dissertation, and, most
recently, looking for a job :-) I've talked to him recently, and he
intends to continue on with the project, as he might have some time to
devote to it.
On a side note, though, one thing that has still not been explored
is compressed _swap_. Since the project's focus has been performance
gains, and it was not clear from the beginning that compressing swap
actually results in performance gains, it still has not been
implemented. That said, this *is* on the project's to-study list.
Hope this helps,
--
Livio B. Soares
next prev parent reply other threads:[~2003-04-27 19:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 22:48 Re: Swap Compression rmoser
2003-04-26 9:17 ` Jörn Engel
[not found] ` <200304261148590300.00CE9372@smtp.comcast.net>
[not found] ` <20030426160920.GC21015@wohnheim.fh-wedel.de>
2003-04-26 23:41 ` Some code for " rmoser
2003-04-27 2:24 ` rmoser
2003-04-27 9:04 ` Jörn Engel
2003-04-27 17:24 ` rmoser
2003-04-27 17:51 ` Jörn Engel
2003-04-27 18:22 ` William Lee Irwin III
2003-04-27 18:31 ` rmoser
2003-04-27 19:04 ` Jörn Engel
2003-04-27 19:57 ` Livio Baldini Soares [this message]
2003-04-27 20:24 ` rmoser
[not found] ` <200304271609460030.01FC8C2B@smtp.comcast.net>
2003-04-27 20:10 ` rmoser
2003-04-27 21:52 ` rmoser
2003-04-27 21:55 ` Re: Swap Compression -- Try 2 rmoser
2003-04-28 8:52 ` Swap Compression Eric W. Biederman
2003-04-28 10:26 ` Jörn Engel
[not found] ` <3EAE8899.2010208@techsource.com>
[not found] ` <200304291521120230.0462A551@smtp.comcast.net>
2003-04-29 19:21 ` rmoser
[not found] ` <3EADAA5D.1090408@techsource.com>
[not found] ` <200304282258310030.00DED562@smtp.comcast.net>
2003-04-29 2:58 ` rmoser
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 22:32 rmoser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030427195731.GA5759@ime.usp.br \
--to=livio@ime.usp.br \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mlmoser@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).