Re: [PATCH 02/23] radixtree: look-aside cache

On Sun, 19 Mar 2006, Wu Fengguang wrote:

> Signed-off-by: Christoph Lameter <[email protected]>

Hmm... This signoff exists because you are using some bit of earlier 
patches by me?

Typically the _node endings mean that one can specify a node number where 
to allocate memory.

Wont partial lookups like this complicate further work on the radixtree? 
Could you  get your speed optimizations into radixtree.c so that others 
can use it in the future?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 02/23] radixtree: look-aside cache
    • From: Wu Fengguang <[email protected]>

• References:
  • [PATCH 00/23] Adaptive read-ahead V11
    • From: Wu Fengguang <[email protected]>
  • [PATCH 02/23] radixtree: look-aside cache
    • From: Wu Fengguang <[email protected]>

• Prev by Date: [PATCH 030/141] V4L/DVB (3432): Hauppauge HVR 900 Composite support
• Next by Date: [PATCH 122/141] V4L/DVB (3394): Bttv: correct bttv_risc_packed buffer size
• Previous by thread: [PATCH 02/23] radixtree: look-aside cache
• Next by thread: Re: [PATCH 02/23] radixtree: look-aside cache
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]