Re: [PATCH 1/1] network memory allocator.

From: Andi Kleen <[email protected]>
Date: Fri, 18 Aug 2006 11:29:14 +0200

> So ideal would be something dynamic to turn on/off io placement, maybe based 
> on node_distance() again, with the threshold tweakable per architecture?

We have this ugly 'hashdist' thing, let's remove the __initdata tag
on it, give it a useful name, and let architectures set it as
they deem appropriate.
-
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/

---

• References:
  • Re: [PATCH 1/1] network memory allocator.
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH 1/1] network memory allocator.
    • From: Christoph Lameter <[email protected]>
  • Re: [PATCH 1/1] network memory allocator.
    • From: Andi Kleen <[email protected]>

• Prev by Date: R: How to avoid serial port buffer overruns?
• Next by Date: Re: [ckrm-tech] [RFC][PATCH 5/7] UBC: kernel memory accounting (core)
• Previous by thread: Re: [PATCH 1/1] network memory allocator.
• Next by thread: Re: [PATCH 1/1] network memory allocator.
• 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]