There is no way in the world this enormous amount of NUMA complexity is being added to the destination cache layer. Sorry. - 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 9/11] net: dst_entry.refcount, use, lastuse to use alloc_percpu
- From: Ravikiran G Thirumalai <[email protected]>
- Re: [patch 9/11] net: dst_entry.refcount, use, lastuse to use alloc_percpu
- References:
- [patch 0/11] mm: Reimplementation of dynamic per-cpu allocator
- From: Ravikiran G Thirumalai <[email protected]>
- [patch 9/11] net: dst_entry.refcount, use, lastuse to use alloc_percpu
- From: Ravikiran G Thirumalai <[email protected]>
- [patch 0/11] mm: Reimplementation of dynamic per-cpu allocator
- Prev by Date: Re: [PATCH 2.6.13 5/14] sas-class: sas_discover.c Discover process (end devices)
- Next by Date: 2.6.14-rc1: oops during boot
- Previous by thread: [patch 9/11] net: dst_entry.refcount, use, lastuse to use alloc_percpu
- Next by thread: Re: [patch 9/11] net: dst_entry.refcount, use, lastuse to use alloc_percpu
- Index(es):
