From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Nitin Gupta <ngupta@vflare.org>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-mm-cc@laptop.org
Subject: Re: [PATCH 1/4] compcache: xvmalloc memory allocator
Date: Wed, 26 Aug 2009 19:19:40 +0300 [thread overview]
Message-ID: <84144f020908260919ke9d6c34qb47c3015ee0ca89b@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0908261209240.9933@gentwo.org>
On Wed, 26 Aug 2009, Nitin Gupta wrote:
>> I went crazy. I meant 40 bits for PFN -- not 48. This 40-bit PFN should be
>> sufficient for all archs. For archs where 40 + PAGE_SHIFT < MAX_PHYSMEM_BITS
>> ramzswap will just issue a compiler error.
On Wed, Aug 26, 2009 at 7:10 PM, Christoph
Lameter<cl@linux-foundation.org> wrote:
> How about restricting the xvmalloc memory allocator to 32 bit? If I
> understand correctly xvmalloc main use in on 32 bit in order to be
> able to use HIGHMEM?
That was the main reason for a specialized allocator rather than
trying to use SLOB. However, if "xvmalloc" is merged with ramzswap, it
makes sense to use it on desktop class 64-bit machines as well.
Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-08-26 16:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 4:37 Nitin Gupta
2009-08-24 17:33 ` Pekka Enberg
2009-08-24 17:52 ` Nitin Gupta
2009-08-24 18:08 ` Pekka Enberg
2009-08-24 18:11 ` Nitin Gupta
2009-08-24 18:27 ` Pekka Enberg
2009-08-24 18:40 ` Nitin Gupta
2009-08-24 19:36 ` Nitin Gupta
2009-08-24 19:43 ` Pekka Enberg
2009-08-24 21:16 ` Nitin Gupta
2009-08-25 4:26 ` Pekka Enberg
2009-08-24 20:39 ` Hugh Dickins
2009-08-24 21:16 ` Nitin Gupta
2009-08-24 21:46 ` Hugh Dickins
2009-08-25 14:52 ` Nitin Gupta
2009-08-25 19:03 ` Nitin Gupta
2009-08-26 16:10 ` Christoph Lameter
2009-08-26 16:17 ` Nitin Gupta
2009-08-26 16:19 ` Pekka Enberg [this message]
2009-08-26 16:07 ` Christoph Lameter
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=84144f020908260919ke9d6c34qb47c3015ee0ca89b@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.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