From: Nitin Gupta <ngupta@vflare.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: 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: Tue, 25 Aug 2009 00:10:34 +0530 [thread overview]
Message-ID: <4A92DEA2.7050000@vflare.org> (raw)
In-Reply-To: <84144f020908241127vc8dafa4l340d000097cf5548@mail.gmail.com>
On 08/24/2009 11:57 PM, Pekka Enberg wrote:
> On Mon, Aug 24, 2009 at 9:11 PM, Nitin Gupta<ngupta@vflare.org> wrote:
>>> Is the name rzmalloc() too similar to kzalloc() which stands for
>>> zeroing allocator, though? I think I suggested
>>> ramzswap_alloc()/ramzswap_free() in the past to avoid confusion. I'd
>>> rather go with that if we can't come up with a nice generic name that
>>> stands for alloc_part_of_page_including_highmem().
>>
>> rzs_malloc()/rzs_free() ?
>
> I am not sure what we gain from the shorter and more cryptic "rzs"
> prefix compared to "ramzswap" but yeah, it's less likely to be
> confused with kzalloc() so I'm okay with that.
>
Perhaps, I'm just too bad with naming :)
xvmalloc -> ramzswap_alloc() (compiled with ramzswap instead of as a separate
module).
BTW, [rzs]control is the name of userspace utility to send ioctl()s to ramzswap.
Somehow, I am happy with rzscontrol name atleast.
Thanks,
Nitin
--
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 3:27 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 [this message]
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
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=4A92DEA2.7050000@vflare.org \
--to=ngupta@vflare.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=linux-mm@kvack.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