From: "Timothy Miller" <tmiller10@cfl.rr.com>
To: "Jan Knutar" <jk-lkml@sci.fi>, <linux-kernel@vger.kernel.org>
Subject: Re: Page compression in lieu of swap?
Date: Sat, 12 Apr 2003 21:59:43 -0400 [thread overview]
Message-ID: <001101c30160$5a9ca790$6801a8c0@epimetheus> (raw)
In-Reply-To: 03041303065500.26409@polaris
From: "Jan Knutar" <jk-lkml@sci.fi>
> On Sunday 13 April 2003 01:35, Timothy Miller wrote:
> > I did some searching of the kernel archives and the only things
> > related to the forthcoming idea had to do with compressing pages when
> > writing to swap and doing compressed disks. Here's a different
> > idea...
>
> http://linuxcompressed.sourceforge.net/
>
> This the same thing?
>
I believe it is!
Anyone on the list checked it out? Is it good? Any benchmarks performed?
Do we want it?
If it doesn't introduce instability, then it could be a very good addition.
Perhaps at the beginning of the 2.7 phase? If were to be in a develoment
kernel for its entire life, it would certainly get all the bugs worked out.
Does Linus have an opinion on it?
One of the things that makes me like Linux the best is that the contributors
really seem to push the envelope. Of course, I don't know really how well
other OS's do in that regard, but I wouldn't be surprised if we were leaving
other OS's like Windows, Solaris, and MacOS in the dust with some of the
cool things being worked on like the O(1) scheduler, the anticipatory I/O
scheduler, etc. Maybe others have such things. <shrug>
Sorry about the rambling.
next prev parent reply other threads:[~2003-04-13 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 22:35 Page compression in lieu of swap? Timothy Miller
2003-04-12 22:50 ` Barry K. Nathan
2003-04-13 0:06 ` Jan Knutar
2003-04-13 1:09 ` Con Kolivas
2003-04-13 1:59 ` Timothy Miller [this message]
2003-04-13 3:12 ` Jan Knutar
-- strict thread matches above, loose matches on Subject: below --
2003-04-13 3:36 Perez-Gonzalez, Inaky
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='001101c30160$5a9ca790$6801a8c0@epimetheus' \
--to=tmiller10@cfl.rr.com \
--cc=jk-lkml@sci.fi \
--cc=linux-kernel@vger.kernel.org \
/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