Messages in this thread | | | Date | Thu, 8 Apr 2004 00:38:09 +0200 | From | Andi Kleen <> | Subject | Re: NUMA API for Linux |
| |
On Wed, 07 Apr 2004 15:38:24 -0700 "Martin J. Bligh" <mbligh@aracnet.com> wrote:
> I think there are some design issues that still aren't resolved - we've > been over this a bit before, but I still don't think they're fixed. > It seems you're still making a copy of the binding structure for every > VMA, which seems ... extravagent. Can we share them? IIRC, the only
Sharing is only an optimization that adds more code and potential for more bugs (hash tables, locking etc.).
We can discuss changes when someone shows numbers that additional optimizations are needed. I haven't seen such numbers and I'm not convinced sharing is even a good idea from a design standpoint. For the first version I just aimed to get something working with straight forward code.
To put it all in perspective: a policy is 12 bytes on a 32bit machine (assuming MAX_NUMNODES <= 32) and 16 bytes on a 64bit machine (with MAX_NUMNODES <= 64)
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |