All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [rfc][patch] radix-tree: direct data
Date: Sun, 23 Apr 2006 04:51:48 +1000	[thread overview]
Message-ID: <444A7B44.1060504@yahoo.com.au> (raw)
In-Reply-To: <20060422183154.GF30503@wotan.suse.de>

Nick Piggin wrote:

> This saves around 16MB in tags on my 4GB G5 with a couple of kernel source
                             ^^^^
Make that `radix_tree_node'

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [rfc][patch] radix-tree: direct data
Date: Sun, 23 Apr 2006 04:51:48 +1000	[thread overview]
Message-ID: <444A7B44.1060504@yahoo.com.au> (raw)
In-Reply-To: <20060422183154.GF30503@wotan.suse.de>

Nick Piggin wrote:

> This saves around 16MB in tags on my 4GB G5 with a couple of kernel source
                             ^^^^
Make that `radix_tree_node'

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

--
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>

  reply	other threads:[~2006-04-22 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22 18:31 [rfc][patch] radix-tree: direct data Nick Piggin
2006-04-22 18:31 ` Nick Piggin
2006-04-22 18:51 ` Nick Piggin [this message]
2006-04-22 18:51   ` Nick Piggin

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=444A7B44.1060504@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.