mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nitin Gupta <ngupta@vflare.org>
To: Christoph Lameter <cl@linux.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	penberg@cs.helsinki.fi, edt@aei.ca, linux-mm-cc@laptop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] compressed in-memory swapping take5
Date: Thu, 2 Apr 2009 09:02:22 +0530	[thread overview]
Message-ID: <d760cf2d0904012032v4b49ccb3gec64c32d4ba4f13f@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0904012207110.32656@qirst.com>

On Thu, Apr 2, 2009 at 7:39 AM, Christoph Lameter <cl@linux.com> wrote:
> On Thu, 2 Apr 2009, Nitin Gupta wrote:
>
>> Justification for this custom allocator is present in xvmalloc changelog
>> itself. It gives reason for not using SLUB and SLOB. During review
>> cycle, I never got any arguments against that justification.
>
> The use of highmem is pretty unique. But that restrict the usefulness to
> 32 bit processors with too much RAM.
>
>

I would again like to mention that apart from highmem, xvmalloc is O(1)
and is very memory efficient too. Sometime in future I hope to present
it as replacement for funny SLOB allocator. For this I will require lot of
data which is another major work....

For now, I will rename xvmalloc to rzmalloc and move it to
drivers/block/ramzswap. As for data to justify ramzswap inclusion
-- its going to be hard. It just 'feels' lot more responsive with compression
but not sure how to quantify this. Maybe I will get some data
by next release.

Thanks to you all for your reviews and suggestions.

Nitin

      reply	other threads:[~2009-04-02  3:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 14:48 Nitin Gupta
2009-03-30 14:50 ` [PATCH 1/3] xvmalloc memory allocator Nitin Gupta
2009-03-30 14:52 ` [PATCH 2/3] ramzswap virtual block device Nitin Gupta
2009-03-30 14:54 ` [PATCH 3/3] ramzswap documentation Nitin Gupta
2009-04-01 22:57 ` [PATCH 0/3] compressed in-memory swapping take5 Andrew Morton
2009-04-02  0:02   ` Nitin Gupta
2009-04-02  2:09     ` Christoph Lameter
2009-04-02  3:32       ` Nitin Gupta [this message]

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=d760cf2d0904012032v4b49ccb3gec64c32d4ba4f13f@mail.gmail.com \
    --to=ngupta@vflare.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=edt@aei.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm-cc@laptop.org \
    --cc=penberg@cs.helsinki.fi \
    /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

Powered by JetHome