public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Asbjørn Sannes" <ace@sannes.org>
To: John Richard Moser <nigelenki@comcast.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Memory compression (again). . help?
Date: Tue, 28 Feb 2006 13:38:16 +0100	[thread overview]
Message-ID: <44044438.5000309@sannes.org> (raw)
In-Reply-To: <44043F8C.7070500@comcast.net>

John Richard Moser wrote:
> >>> I'm not quite sure what I'm doing or when I have time, but I'm looking
> >>> into writing in some hooks and a compression routine to manage
> >>> compressed memory.
<snip>
> I'm actually looking to submit to mainline in the end ;P  It'd be a very
> good permenant feature.  RAM is cheap, but CPU is even cheaper; if I buy
> a gig of RAM and get 200M free, woohoo?

Nitin Gupta and myself has already started working on a implementation
for 2.6, you are of course welcome to join our effort. Nitin has already
made some code available where you can clearly see where such things
could be done. I can recommend "Understanding the Linux kernel (3rd
Edition)" by Daniel P. Bovet & Marco Cesati. Also, you could take a look
at http://www.kernelnewbies.org/ under recommended books.


Mvh,
Asbjørn Sannes


  reply	other threads:[~2006-02-28 12:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28  1:03 Memory compression (again). . help? John Richard Moser
2006-02-28  3:27 ` John Richard Moser
2006-02-28  5:20   ` Magnus Damm
2006-02-28 12:06     ` John Richard Moser
2006-02-28 16:24   ` Rik van Riel
2006-02-28 17:02     ` John Richard Moser
2006-02-28  4:00 ` Alexander E. Patrakov
2006-02-28 12:18   ` John Richard Moser
2006-02-28 12:38     ` Asbjørn Sannes [this message]
2006-02-28 16:06       ` John Richard Moser

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=44044438.5000309@sannes.org \
    --to=ace@sannes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@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